top | item 27501450

(no title)

thomasedwards | 4 years ago

I love that you looked at this website, saw its <table> layout, saw the copyright was the year 2000, saw the images with terrible drop shadows, the freeservers icon in the top, and thought “uh, weird this isn’t https”.

discuss

order

defaultname|4 years ago

More likely they have HTTPS-only on so it turns into a error condition. Thankfully such sites are rare now.

Aside: Paul Graham's blog that is frequently front-paged on here doesn't support HTTPS. That has always seemed odd.

tialaramex|4 years ago

I too have HTTPS-only set, it's interesting what isn't HTTPS in 2021.

http://www.open-std.org/ is the site that maintains lots of documents for the Joint Technical Committee ISO/IEC JTC 1.

Historically both ISO and the IEC worked on IT standards. But obviously it's no good if there's an ISO international standard for how to encode the letter 'A' as binary data and a separate IEC standard for how to do it. In the best case this is pointless duplication of effort (these are international standards groups, every country is ultimately involved) and in the worst case they diverge and there's actual conflict, defying the purpose of standardization. So, the Joint Technical Committee does work on this intersection on behalf of both IEC and ISO.

Now, the importance of these standards to everybody means it certainly can be argued that the site must remain forever accessible to those without HTTPS but it's hard to think of any reason to just not implement HTTPS at all...

Ashanmaril|4 years ago

It's not even written in React!