HTTPS on Stack Overflow: The End of a Long Road

Re:HTTPS on Stack Overflow: The End of a Long Road by TorKlingberg on Monday May 22, 2017 @12:28PM (#14394882)

I feel like TLS certificates are fundamentally misdesigned there. It should be possible to have a wildcard certificate that matches all subdomains under a domain, no matter how many layers deep.

[ Parent | on HN ]

Re:HTTPS on Stack Overflow: The End of a Long Road by Nick-Craver on Monday May 22, 2017 @01:05PM (#14395205)

Well if it wasn't for someone buying <star>.com back in the day, we probably could have them. Oh and then buying <star>.<star>.com after browsers banned that one, which led to RFC 6125 rule clarifications and restrictions.

[ Parent | on HN ]

Re:HTTPS on Stack Overflow: The End of a Long Road by DamonHD on Monday May 22, 2017 @01:55PM (#14395614)

Hey, I'm pretty sure that the first real domain name hack was sex.net, which as the proud owner of ex.net [PS: or was it sexnet.com, as we also have exnet.com?] caused some upset for a while, though mainly to disappointed one-handed typists I believe... B^>

BTW, did I blink and miss the "It really is all faster over HTTP/2, even given TLS" bit? My testing for my tiny lightweight sites close to their users (the opposite of what you're dealing with) is that HTTP/2 is slightly slower overall. Even with Cloudflare's advantages such as good DNS. And with the pain of cert management...

http://m.earth.org.uk/note-on-carbon-cost-of-CDN.html

Anyhow, thanks for the warts-n-all.

[ Parent | on HN ]

Re:HTTPS on Stack Overflow: The End of a Long Road by knodi123 on Tuesday May 23, 2017 @01:34AM (#14399014)

> which as the proud owner of ex.net

haha, that page is a priceless timecapsule:

Use the Java applet below to search ExNet's main Web pages.

When the ``Status'' indicator stops flashing and says ``Idle'', type key words in the ``Search for:'' box.

The ``Results:'' box will show you the documents that matched your key words, the best matches coming first in the list. Click on any line in the ``Results:'' box, and that document should appear in a new browser window in a few seconds. When you are finished with that document, you can close it without killing your browser.

[ Parent | on HN ]

Re:HTTPS on Stack Overflow: The End of a Long Road by DamonHD on Tuesday May 23, 2017 @01:51AM (#14399085)

That code did search-by-word from (IIRC before Google existed, ie Netscape 2) right up until Java applets were dropped, across all compliant browsers AFAIK. It did roughly what G's live search now does.

[ Parent | on HN ]

Re:HTTPS on Stack Overflow: The End of a Long Road by eridius on Monday May 22, 2017 @03:06PM (#14396095)

I would imagine the more resources your page has, the more benefit you can get from HTTP/2 because of Server Push. So if you're comparing a tiny lightweight site, I'm guessing you can't benefit as much from Server Push.

[ Parent | on HN ]

Re:HTTPS on Stack Overflow: The End of a Long Road by DamonHD on Monday May 22, 2017 @04:39PM (#14396757)

I have relatively little that would benefit from push; basically a tiny hand-crafted CSS file that I currently inline because HTTP/1.1 and even HTTP/2 overhead for having it separate may be too high.

[ Parent | on HN ]