Post B6IEHH8XUHPFTrMCy8 by ltning@pleroma.anduin.net
 (DIR) More posts by ltning@pleroma.anduin.net
 (DIR) Post #B6EAQaASvHKef5bJya by Markus@oldbytes.space
       0 likes, 0 repeats
       
       #retrocomputing  #vintagecomputing  #search #searchengine  #frogfind #NetBSD #arcticfox #unix Catch of the Day: "Of course it runs NetBSD!" 🐡🦊Hey Retro Fans!Did you have a good weekend? Our bouncer at the FrogFind pond was certainly busy and waved a guest through yesterday that put a massive smile on our faces:ArcticFox 52.9 on NetBSD!Among hardcore Unix nerds, there is a famous catchphrase: "Of course it runs NetBSD!" This open-source operating system is legendary for its portability. It has been ported to run on almost anything with a processor—from old toasters and Sega Dreamcasts to massive server racks.The fact that someone navigated to our pond using NetBSD is already awesome. But the combination with the ArcticFox browser makes it a masterpiece. ArcticFox is a lovingly maintained community fork (based on Pale Moon) specifically kept alive to enable modern browsing on exotic architectures, PowerPC Macs, and old UNIX derivatives.Cheers to the tinkerers keeping exotic systems online!Your FrogFind Team 🐸
       
 (DIR) Post #B6EAQaVjeCLVj3YJ84 by ltning@pleroma.anduin.net
       0 likes, 0 repeats
       
       @Markus Hey there! I've had a bit of trouble with FrogFind on IBM WebExplorer/2 because of the Content-Type header you (sometimes?) return. If the charset=utf8 is added, that browser refuses to render the file and rather offers to download it. I've solved this by throwing a proxy in the mix, but that's somewhat impractical. Anything you can do? :)
       
 (DIR) Post #B6EAQai8u4GqLXMDT6 by Markus@oldbytes.space
       0 likes, 1 repeats
       
       @ltning Hey there! 🐸First of all: Thank you so much for this amazing feedback! Hearing that someone is actively using FrogFind on an original IBM WebExplorer under OS/2 absolutely made my day. This is exactly the kind of retro-magic FrogFind was built for!You totally nailed the issue. Early browsers like the WebExplorer have a very strict/primitive MIME-type parser. When it sees text/html;charset=utf-8, it trips over the semicolon and the charset definition, doesn't recognize the string, and defaults to offering a file download instead of rendering the page.I will be applying a fix during the next hours. The server then checks the User-Agent. If it detects the WebExplorer, it completely strips the charset definition and serves a pure, naked Content-Type: text/html header.You should be able to ditch your proxy now and surf directly. Please give it a try and let me know if WebExplorer behaves nicely again!Thanks for the bug report and for keeping OS/2 Warp alive! 🚀
       
 (DIR) Post #B6IEHH8XUHPFTrMCy8 by ltning@pleroma.anduin.net
       0 likes, 0 repeats
       
       @Markus Hey, I just tried with WebEx 1.1h, and it still complains about the same thing :-/Never mind, I was using .com. Which isn't fixed (obviously).However I have another problem - I don't think WebEx is providing a Host: header, so all I get is "Hier ensteht eine neue Internetpräsenz..." with links to 1blu :)
       
 (DIR) Post #B6IEHHPCUKjYJX9VwG by ltning@pleroma.anduin.net
       0 likes, 1 repeats
       
       @Markus Check this out ;)