One random thing that really annoys me is that the site http://shakespeare.mit.edu does not properly forward http requests to https although they have an https version of the site.
At least because search engines rank TLS enabled sites higher these days. And also, wrapping everything in TLS creates more noise against surveillance and makes surveillance more expensive.
SSL (or TLS nowadays) not only protects against surveillance but also guarantees the integrity of the data you send and receive. Without it, someone could spoof the response you receive. In practice this means injecting ads or malware or even worse: fake shakespeare!
Funniest thing I’ve ever seen is the docs for Nginx do the same, no http to https redirection. I mean, you would hope that the maintainers for the biggest web server in the world would be able to manage that but somehow… No they don’t.
No, an .htaccess file is specific to Apache HTTP Server… although some other web servers have integrated the format. However, most browsers now automatically redirect when an HTTPS version exists.
One random thing that really annoys me is that the site http://shakespeare.mit.edu does not properly forward http requests to https although they have an https version of the site.
Why does reading Shakespeare need to be over SSL?
At least because search engines rank TLS enabled sites higher these days. And also, wrapping everything in TLS creates more noise against surveillance and makes surveillance more expensive.
SSL (or TLS nowadays) not only protects against surveillance but also guarantees the integrity of the data you send and receive. Without it, someone could spoof the response you receive. In practice this means injecting ads or malware or even worse: fake shakespeare!
According to some, all Shakespeare is fake Shakespeare.
Funniest thing I’ve ever seen is the docs for Nginx do the same, no http to https redirection. I mean, you would hope that the maintainers for the biggest web server in the world would be able to manage that but somehow… No they don’t.
server serves a protocol on a port. I would rather it not include logic like that. turn off the http port of you don’t want to serve http.
Apache tomcat had a stupid security issue. I recently did a HackTheBox about it. Here’s a write-up of the box https://medium.com/ctf-writeups/hack-the-box-jerry-write-up-6f045601315f
If you are using Firefox, enable https everywhere setting and it fixes stuff like that
It will only give an error if there’s no https version that exists
deleted by creator
Don’t you just need to toss an “.htaccess” file in the root?
No, an .htaccess file is specific to Apache HTTP Server… although some other web servers have integrated the format. However, most browsers now automatically redirect when an HTTPS version exists.