Forum Moderators: open

Message Too Old, No Replies

W3c 503

         

iamlost

3:59 am on Jun 2, 2021 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



The W3C (World Wide Web Consortium) site w3 org currently returns:

503 Service Unavailable

Word is that a bit earlier browsers were reporting certificate expired.

Yet another reminder that certs are a critical component of TLS (HTTPS).

Of course one could retain plain vanilla HTTP in parallel or as a fallback rather than simply 301-ing it to https.

Unfortunately browsers these days like to call such insecure even where there really is nothing (on the site) to secure; there may be a mitm! a monster under the bed!
Browsers as helicopter parents.

lucy24

4:41 am on Jun 2, 2021 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



They're back now.

browsers these days like to call such insecure even where there really is nothing (on the site) to secure
The browser can’t know that. It only knows that the site wants to be secure but hasn’t done it right.

iamlost

5:24 am on Jun 2, 2021 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Good to see this resolved in such a timely fashion.


It only knows that the site wants to be secure but hasn’t done it right.

In this case W3C was apparently running HSTS (HTTP Strict Transport Security) that tells clients they should always connect to your server via HTTPS, even when following an HTTP reference.
Note: the benefits are (1) it saves the otherwise necessary 301 of http to https, and (2) defeats attacks such as SSL Stripping, ISP ad injection, etc.

Which, matches with your quoted comment above.

However, what I meant was that browsers increasingly mark http served sites as insecure.

Also, while most sites use a third party host and have little to no choice those running their own server can run both HTTPS and HTTP in parallel as they use separate ports and/or normally redirect from HTTP to HTTPS with a failover from HTTPS to HTTP when required. Not seen too often but is done occasionally where visitor PII input is not required.

Perhaps too many info vectors in one comment? Racing off in all directions? I resemble that remark...

lammert

9:02 am on Jun 2, 2021 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



They use a domain validation SSL certificate. This would have been a nice opportunity to move to Let's Encrypt and automate the SSL renewal process.