4 ms·

I think you're confused about the context in which they are not yet supporting HTTP/3: they are deciding to hold off on serving it, not on allowing it to pass t

by jefftk 4y ago

I think you're confused about the context in which they are not yet supporting HTTP/3: they are deciding to hold off on serving it, not on allowing it to pass through their network: All of this is of course academic until Ubuntu's version of Apache supports HTTP/3. We're quite unlikely to switch web servers to get HTTP/3 They're worried some of their users will be in environments that don't properly support QUIC, and if they started serving HTTP/3 today they might have more support hassle.

comex 4y ago
If you click the link in the blog post with the text “firewalls need adjustments to let 'QUIC' traffic through”, it seems like there is some of the latter as well. Well, not holding off on allowing it through their network, per se, but being worried that their overly complex firewall setup hasn’t been properly adjusted to allow it through their network in all cases.
- deleted 4y ago
  [deleted]
jeroenhd 4y ago
I would've accepted that train of thought if it wasn't for their earlier posts about how HTTP/3 is making their lives more difficult. I don't know what's happening to their firewall, but these people seem to run into HTTP/3 problems all the time. There's a difference between "I'm not switching to electric cars yet" and "I'm not switching to electric cars yet after I've burned down my house three times installing electric chargers". Their network is somehow horribly broken and that leads them to pain a picture as if the protocol is somehow inherently stable or problematic to turn on. They're projecting their own misconfiguration onto the wider internet as a whole, and this is exactly the kind of behaviour that has led to the protocol ossification we see today.
- jefftk 4y ago
  Is this the earlier post you were thinking of? https://utcc.utoronto.ca/~cks/space/blog/sysadmin/HTTP3AndOurFirewalls https://utcc.utoronto.ca/~cks/space/blog/sysadmin/HTTP3AndOu... I think that post is much less reasonable, but it's also almost 2 years old and they may not be doing that kind of blocking anymore?
  - jeroenhd 4y ago
    I think they must've stopped blocking HTTP/3 at some point because the author has had other HTTP/3 related issues they posted about since. However, as of this post: https://utcc.utoronto.ca/~cks/space/blog/sysadmin/WireGuardForFirewallBypass https://utcc.utoronto.ca/~cks/space/blog/sysadmin/WireGuardF... I think it's still safe to consider their network setup hasn't changed much.

by jefftk 4y ago

comex 4y ago

If you click the link in the blog post with the text “firewalls need adjustments to let 'QUIC' traffic through”, it seems like there is some of the latter as well. Well, not holding off on allowing it through their network, per se, but being worried that their overly complex firewall setup hasn’t been properly adjusted to allow it through their network in all cases.

deleted 4y ago
[deleted]

jeroenhd 4y ago

I would've accepted that train of thought if it wasn't for their earlier posts about how HTTP/3 is making their lives more difficult. I don't know what's happening to their firewall, but these people seem to run into HTTP/3 problems all the time. There's a difference between "I'm not switching to electric cars yet" and "I'm not switching to electric cars yet after I've burned down my house three times installing electric chargers". Their network is somehow horribly broken and that leads them to pain a picture as if the protocol is somehow inherently stable or problematic to turn on. They're projecting their own misconfiguration onto the wider internet as a whole, and this is exactly the kind of behaviour that has led to the protocol ossification we see today.

jefftk 4y ago
Is this the earlier post you were thinking of? https://utcc.utoronto.ca/~cks/space/blog/sysadmin/HTTP3AndOurFirewalls https://utcc.utoronto.ca/~cks/space/blog/sysadmin/HTTP3AndOu... I think that post is much less reasonable, but it's also almost 2 years old and they may not be doing that kind of blocking anymore?
- jeroenhd 4y ago
  I think they must've stopped blocking HTTP/3 at some point because the author has had other HTTP/3 related issues they posted about since. However, as of this post: https://utcc.utoronto.ca/~cks/space/blog/sysadmin/WireGuardForFirewallBypass https://utcc.utoronto.ca/~cks/space/blog/sysadmin/WireGuardF... I think it's still safe to consider their network setup hasn't changed much.