adlai: is there no way to politely tell an HTTP 301 parrot to fuck off with the TLS and serve the insecure static page over HTTP?
adlai has spent the past monomaniac fixnum count of ticks asking search engines this question, and repeatedly everything misinterprets the question as "how to request HTTPS", "how to avoid protocol downgrade attacks", etc
adlai: one result for configuring the server, although that is also not what I asked
adlai: it's amazing how useless search engines are, sometimes. helpfully useless and ever so optimistic.
adlai: of course one can simply not follow the 300-level redirects, although somehow I suspect that servers are deaf to that
shinohai: http://logs.nosuchlabs.com/log/asciilifeform/2021-02-13#1031522 <<< it be so decreed that HTTP 301 parrots fuck off and go to https://imgur.com/H5Ahsc2
snsabot: Logged on 2021-02-13 16:06:12 adlai: is there no way to politely tell an HTTP 301 parrot to fuck off with the TLS and serve the insecure static page over HTTP?
adlai was hoping for an HTTP request header, along the lines of "Accept-Methods: HTTP", that simply declares a refusal to use TLS
shinohai: Ahh so something more along lines of https://www.youtube.com/watch?v=z9SMUzj-_4Q
shinohai: so all TLS stone ded
adlai actually has no opposition to some form of site encryption ! yet shouldn't it be possible to prefix a request with "don't bother negotiating encryption and authentication, Herr Goebbles reads over my shoulder, and I can't afford to melt my computer with thermite between each time he blinks"
verisimilitude: Try using wget, adlai.
verisimilitude: I'm routinely surprised at how terrible the WWW browser HTTP clients are.
adlai: it's probably the kind of request that would fall stillborn in any modern standards committee, what with the whole "encrypt everything" fashion
adlai: so, I am not terribly surprised that there are no headers for declaring this; although, still mildly so!
trinque: likely gotta recompile without.