← Back to context Comment by ahoka 6 hours ago Anyone else blocks UDP 80/443 due to privacy concerns? 6 comments ahoka Reply detaro 6 hours ago What privacy concern do you have that does not apply to TCP 80/443? ahoka 6 hours ago Tracking sessions across different physical connections has some non-trivial privacy implications:https://http3-explained.haxx.se/en/quic/quic-connections#con... NavinF 6 hours ago How do you imagine other protocols handle switching physical connections? With HTTP 1, you send your session ID as a cookie after wasting time creating a new TCP connection 1 reply → MallocVoidstar 6 hours ago No. frmdstryr 2 hours ago Yes, no performance difference either.
detaro 6 hours ago What privacy concern do you have that does not apply to TCP 80/443? ahoka 6 hours ago Tracking sessions across different physical connections has some non-trivial privacy implications:https://http3-explained.haxx.se/en/quic/quic-connections#con... NavinF 6 hours ago How do you imagine other protocols handle switching physical connections? With HTTP 1, you send your session ID as a cookie after wasting time creating a new TCP connection 1 reply →
ahoka 6 hours ago Tracking sessions across different physical connections has some non-trivial privacy implications:https://http3-explained.haxx.se/en/quic/quic-connections#con... NavinF 6 hours ago How do you imagine other protocols handle switching physical connections? With HTTP 1, you send your session ID as a cookie after wasting time creating a new TCP connection 1 reply →
NavinF 6 hours ago How do you imagine other protocols handle switching physical connections? With HTTP 1, you send your session ID as a cookie after wasting time creating a new TCP connection 1 reply →
What privacy concern do you have that does not apply to TCP 80/443?
Tracking sessions across different physical connections has some non-trivial privacy implications:
https://http3-explained.haxx.se/en/quic/quic-connections#con...
How do you imagine other protocols handle switching physical connections? With HTTP 1, you send your session ID as a cookie after wasting time creating a new TCP connection
1 reply →
No.
Yes, no performance difference either.