4 ms·
Somewhat off-topic. This is the first page that I have encountered that has given me a insufficient TLS error. I'm using 1.2 because apparently I'm somewhere
by Lerc 2y ago
Somewhat off-topic. This is the first page that I have encountered that has given me a insufficient TLS error.
I'm using 1.2 because apparently I'm somewhere that causes pytorch.org and some other github.io connections to break on Chrome and Firefox using 1.3. Something to do with packet splitting on connection I think. Curl was lean enough to work with 1.3. Might go back to 1.3 and see if the Github pages work now. [edit: whatever it was seems to be fixed, I can read pytorch.org docs again using TLS 1.3]
Remember when computers used to just work? Yeah, me neither.
- mmastrac 2y agoAre you sure you aren't being MITM downgraded? I didn't think TLS 1.3 was packet-boundary aware.
- Lerc 2y agoNot sure about MITM, no proof against it but seems hardly likely. It might have been some weird attempt to reduce latency. Wireshark seemed to show responses that were sent before the request that triggered it had finished transmitting. The handshake seemed really shuffled out of order. Watching curl do the handshake sent far fewer bytes.