2 ms·
This is meh excuse. If you want your browser to connect to a gopher server, you type gopher://example.com. If you want to use http2, http2://example.com shoul
by jrockway 2y ago
This is meh excuse. If you want your browser to connect to a gopher server, you type gopher://example.com. If you want to use http2, http2://example.com should work. (I know, I know, everyone removed Gopher support a few years ago. Same idea though.)
Having said all that, I just copied the certs out of here https://cs.opensource.google/go/go/+/refs/tags/go1.24.0:src/net/http/internal/testcert/testcert.go https://cs.opensource.google/go/go/+/refs/tags/go1.24.0:src/... and use them to do browser/http2 stuff locally. Why steal Go's certificates? Because it took 1 second less than making my own!
- taftster 2y agoHey, thanks for this. It saves me even more than 1 second!
- e12e 2y agoWhich browsers/libraries trust these? Or does the go tool chain install them?
- jrockway 2y agoNothing trusts them, they're just regular self-signed certificates. There is no benefit to using these over your own self-signed certificates except that you don't have to ask your LLM for the commands to generate them ;)
- e12e 2y agoAnd of course once you trust them on localhost, you expose yourself to some risk, since the whole world can get a copy of the key.
- johannes1234321 2y agoUsing http2 as protocol in the URL makes the initial transition complex: One can't share links between different users and clients and from other websites with a guarantee of the "best" experience for the user. Not to mention all old links outside the control of the server operator.