4 ms·

I loaded up Windows 98SE SP2 in a VM and tried to use it to browse the modern web but it was basically impossible since it only supported HTTP/1.1 websites. I w

by edm0nd 1y ago

I loaded up Windows 98SE SP2 in a VM and tried to use it to browse the modern web but it was basically impossible since it only supported HTTP/1.1 websites. I was only able to find maybe 3-4 websites that still supported it and load.

ronsor 1y ago
I would expect your main problem to be SSL/TLS. As far as I know, even modern web servers have no problem serving content to HTTP/1.0 clients.
- karel-3d 1y ago
  I tried old macOS ... sorry, Mac OS ... and yeah the main problem was SSL/TLS. HTTP/1.0 was fine but the SSL crypto algorithm negotiation never went through.
- JdeBP 1y ago
  In theory, yes, although there are some fairly big stones falling in the avalanche of turning off HTTP/0.9 and HTTP/1.0 at the server end. In practice, it's going to be tricky to know without measurement; and the shifting of the default at the client end to from 0.9 and 1.0 to 1.1 began back in 2010. Asking the people who run robots for statistics will not help. Almost no good actor robots are using 0.9 and 1.0 now, and 0.9 and 1.0 traffic dropped off a cliff in the 2010s falling to 0% (to apparently 1 decimal place) by 2021 as measured by the Web Almanac. * https://almanac.httparchive.org/en/2021/http https://almanac.httparchive.org/en/2021/http If a modern HTTP server stopped serving 0.9 and 1.0, or even just had a problem doing so to decades-old pre-1.1 client softwares, very few people would know. Almost 0% of HTTP client traffic would be affected. And, indeed, http://url.town/ http://url.town/ is one of the very places that has already turned 0.9 off. It does not speak it, and returns a 1.1 error response. And no-one in this thread (apart from edm0nd) knew.
anthk 1y ago
Try Retrozilla https://portal.mozz.us/gopher/gopher.somnolescent.net/9/w2krepo/web-browsers/retrozilla-2.2.en-US.win32.installer.exe?raw=1 https://portal.mozz.us/gopher/gopher.somnolescent.net/9/w2kr... with these NEW values in about:config set to true: security.ssl3.ecdhe_ecdsa_aes_128_gcm_sha256 security.ssl3.ecdhe_rsa_aes_128_gcm_sha256 Also, set these to false: security.ssl3.ecdh_ecdsa_rc4_128_sha security.ssl3.ecdh_rsa_rc4_128_sha security.ssl3.ecdhe_ecdsa_rc4_128_sha security.ssl3.ecdhe_rsa_rc4_128_sha security.ssl3.rsa_rc4_128_md5 security.ssl3.rsa_rc4_128_sha

by edm0nd 1y ago

ronsor 1y ago

I would expect your main problem to be SSL/TLS. As far as I know, even modern web servers have no problem serving content to HTTP/1.0 clients.

karel-3d 1y ago
I tried old macOS ... sorry, Mac OS ... and yeah the main problem was SSL/TLS. HTTP/1.0 was fine but the SSL crypto algorithm negotiation never went through.
JdeBP 1y ago
In theory, yes, although there are some fairly big stones falling in the avalanche of turning off HTTP/0.9 and HTTP/1.0 at the server end. In practice, it's going to be tricky to know without measurement; and the shifting of the default at the client end to from 0.9 and 1.0 to 1.1 began back in 2010. Asking the people who run robots for statistics will not help. Almost no good actor robots are using 0.9 and 1.0 now, and 0.9 and 1.0 traffic dropped off a cliff in the 2010s falling to 0% (to apparently 1 decimal place) by 2021 as measured by the Web Almanac. * https://almanac.httparchive.org/en/2021/http https://almanac.httparchive.org/en/2021/http If a modern HTTP server stopped serving 0.9 and 1.0, or even just had a problem doing so to decades-old pre-1.1 client softwares, very few people would know. Almost 0% of HTTP client traffic would be affected. And, indeed, http://url.town/ http://url.town/ is one of the very places that has already turned 0.9 off. It does not speak it, and returns a 1.1 error response. And no-one in this thread (apart from edm0nd) knew.

anthk 1y ago

Try Retrozilla https://portal.mozz.us/gopher/gopher.somnolescent.net/9/w2krepo/web-browsers/retrozilla-2.2.en-US.win32.installer.exe?raw=1 https://portal.mozz.us/gopher/gopher.somnolescent.net/9/w2kr... with these NEW values in about:config set to true: security.ssl3.ecdhe_ecdsa_aes_128_gcm_sha256 security.ssl3.ecdhe_rsa_aes_128_gcm_sha256 Also, set these to false: security.ssl3.ecdh_ecdsa_rc4_128_sha security.ssl3.ecdh_rsa_rc4_128_sha security.ssl3.ecdhe_ecdsa_rc4_128_sha security.ssl3.ecdhe_rsa_rc4_128_sha security.ssl3.rsa_rc4_128_md5 security.ssl3.rsa_rc4_128_sha