News for hackers. Stuff that matters.
Re:WebSockets vs. Server-Sent-Events vs. Long-Polling vs. We... by 0x457 on Monday March 18, 2024 @03:45PM (#39749069)
> As long as browsers still work with TCP, some networks will continue to block UDP (and thus HTTP3/WebTransport) outright.

I keep hearing it, but I've never actually seen such a network. There are many things that run on UDP. I can see it being closed in some tiny offices (but those usually lack brain power to accomplish it) or some dystopian corporate offices you can only see in a movie.

I really don't see how the fact that some networks might ban UDP has anything to do with it. Some networks ban google.com and wikipedia.com, you don't see them failing.

Re:WebSockets vs. Server-Sent-Events vs. Long-Polling vs. We... by apitman on Monday March 18, 2024 @03:50PM (#39749123)
In their excellent article on NAT traversal[0], Tailscale mentions that the UC Berkeley guest wifi blocks all outbound UDP except DNS.

EDIT: According to this[1] issue, Berkeley guest wifi allows port 443, which would solve HTTP3/WebTransport. That's certainly hopeful, and I hope all networks are like this in the future. It's just not a forgone conclusion yet.

[0]: https://tailscale.com/blog/how-nat-traversal-works#have-you-...

[1]: https://github.com/danderson/natlab/issues/1

Re:WebSockets vs. Server-Sent-Events vs. Long-Polling vs. We... by gorjusborg on Tuesday March 19, 2024 @09:43AM (#39755652)
That's a case of shipping it 'broken' for those people.

If it works literally everywhere else, and the product is valuable, they'll change.

Re:WebSockets vs. Server-Sent-Events vs. Long-Polling vs. We... by CodesInChaos on Monday March 18, 2024 @03:53PM (#39749140)
Not a traditional network, but Tor doesn't support UDP.