3 ms·
Certainly they can be installed on the VM, doesn't mean that the VM has network drivers installed. Separately, very old browsers only talk HTTP 1.0 (No Host: h
by sbierwagen 6y ago
Certainly they can be installed on the VM, doesn't mean that the VM has network drivers installed.
Separately, very old browsers only talk HTTP 1.0 (No Host: header support, so they can't connect to non-dedicated servers) and no modern ciphersuites. (Can't connect to HSTS servers that disallow insecure ciphers)
- anthk 6y agoBut they support Gopher. And Clazilla exists.
- deleted 6y ago[deleted]
- hnlmorg 6y agoHTTP 1.1 was released before Mac OS 8 so I'd be surprised if the installed browsers didn't have header support (shared hosting was already common when I used to support Mac OS 8 systems and those users certainly never had a problem). TLS would be a bigger issue at the protocol layer and with the web moving to HTTPS everywhere, you'd expect a great deal of sites not to load. On the rendering side, HTML 5, CSS 3 etc weren't around. In fact I don't even think HTML 4 was around (or if it was, it would have been extremely new so still unlikely to be well supported -- remember how long it took browsers to pass the ACID tests?). Back then it was still common to use framesets and tables for formatting. Ironically, you'd probably get a better experience elinks or lynx.
- rzzzt 6y agoThere was a project floating around recently that rendered the website as an image using a modern browser backend, transmitted it back to any old browser (was demonstrated using IE5, I think), and also mapped mouse clicks to the appropriate locations in the document so the page remained more or less interactive. The UI looked like an extra navigation bar. Can't remember the name, though (and it's also hard to search for). edit: browser history to the rescue, it's https://github.com/ttalvitie/browservice https://github.com/ttalvitie/browservice