3 ms·
That's weird, if I open that link in Firefox (though with the HTTPS-only mode on), Tor Browser with default settings, and Ungoogled Chromium with default settin
by Vecr 4y ago
That's weird, if I open that link in Firefox (though with the HTTPS-only mode on), Tor Browser with default settings, and Ungoogled Chromium with default settings, it 404s (after going to a https link). If I directly wget on the http link it works though.
- 1vuio0pswjnm7 4y agoI also force all http to https using a proxy and I get a 404, too. If want to use https to retrieve the PDF, can use Wikiwix cache: https://archive.wikiwix.com/cache/index2.php?rev_t=9999999999999999999999&url=http%3A%2F%2Fwww.columbia.edu%2F~hauben%2Fbook-pdf%2FCHAPTER%2010.pdf https://archive.wikiwix.com/cache/index2.php?rev_t=999999999... PDF looks like crap anyway. Here's the original text-only version, available via https: https://web.archive.org/web/20111215195747if_/http://www.columbia.edu/~rh120/ch106.x10 https://web.archive.org/web/20111215195747if_/http://www.col...
- saurik 4y agoAs http and https are separate origins, and this website might want to have secure cookies, I'm guessing that a while back they started moving to a more modern / secure web stack but had to figure out how to deal with legacy ~ URLs and made the decision not to break all of those URLs but instead just continue to serve them only as http and then have the rest of the website redirect to https. The reality is that, if you insist on redirecting http to https even when the underlying website doesn't want you to, you are going to end up with a broken experience sometimes and it frankly isn't notable.