3 ms·
HTTPS encrypts the contents of the request. The things requested still happen in plain text.
by dotancohen 7y ago
HTTPS encrypts the contents of the request. The things requested still happen in plain text.
- tialaramex 7y agoMost of the request is encrypted. Suppose you type https://foo.example.com/bar?baz#quux https://foo.example.com/bar?baz#quux into your browser Most TLS (TLS up to 1.2) will tell anybody who is watching that you visited foo.example.com including the SNI foo.example.com your browser sent to tell the server which name it was looking for and the certificate the server provided to prove it is really foo.example.com. But it will encrypt bar and baz and quux isn't sent over the wire it's just used internally by the browser and any Javascript. That's the difference between "dotancohen looked at webMD" and "dotancohen looked at this article about sexually transmitted infections in men who have sex with men". In TLS 1.3 the certificate is encrypted, a snooper can still see you asked for foo.example.com but not whether this server in fact presented a certificate for that name. eSNI (currently under active development as an addition to TLS 1.3) encrypts that part where your browser asks for foo.example.com, since your browser also did a DNS lookup for foo.example.com we need to encrypt that too for it is make any real difference which is being done under DPRIVE.
- dotancohen 7y agoThank you. I was simplifying, but in fact DPRIVE is new to me.