4 ms·
w3.org redirect to www.w3.org, but not HTTPS. This makes sense for the standards org that defines HTTP, and needs to maintain backwards compatibility.
by chuckhoupt 7y ago
w3.org redirect to www.w3.org, but not HTTPS. This makes sense for the standards org that defines HTTP, and needs to maintain backwards compatibility.
- jcranmer 7y agoExcept the standards org that defines HTTP is the IETF, not the W3C...
- chuckhoupt 7y agoOpps! You're right, the W3C only helped author it. I was also wrong to say that w3.org never redirects to HTTPS. If the browsers sends a Upgrade-Insecure-Requests HTTP-header, then it redirects. That allows it to support all browsers as securely as possible. Sites like whynohttps.com and observatory.mozilla.org should really test for this pattern.