4 ms·
Just because there is something on this domain listening on :443 and serving HTTPS, doesn't mean it has to serve the same content as the HTTP on :80, or even wo
by q3k 6y ago
Just because there is something on this domain listening on :443 and serving HTTPS, doesn't mean it has to serve the same content as the HTTP on :80, or even work at all.
Always-redirect-to-HTTPs plugins _are_ broken by assuming otherwise.
- seba_dos1 6y ago> doesn't mean it has to serve the same content as the HTTP Of course, that's the exact reason I wrote the original comment.
- AgoRapide 6y agoAuthor here. I took a look in IIS Admin and is unable to see WHERE did I ask it to serve https. I thought I was http only. The bindings only say http, both for the bef.no site and for the 'Default Web Site'.