melroy , (edited ) to random
@melroy@mastodon.melroy.org avatar
melroy , to random
@melroy@mastodon.melroy.org avatar

@georgengelmann Sorry I didn't follow-up right away, I was kinda busy. I don't think this is my issue. I do have quic enabled, but only one the default server block in Nginx (listen 443 quic reuseport default_server;). For all my other domains I use: http2 on; http3 on;, which should go to HTTP/3 when possible. Yet, in all cases it uses HTTP/2 for all my resources :(...

melroy OP ,
@melroy@mastodon.melroy.org avatar

@georgengelmann I'm still busy with it. I got some help from @debounced . http3 on; seems non existing anymore. So you need to use "listen 443 quic" on other domain confs. That being said, I still don't get HTTP/3 working. And just yesterday also forked to http://freenginx.org/

melroy OP ,
@melroy@mastodon.melroy.org avatar

@georgengelmann @debounced I think I found the problem. I was using the official Nginx packages from http://nginx.org/packages/mainline/ubuntu/ which didn't had the ngx_http_v3_module compiled... Omg.

melroy OP ,
@melroy@mastodon.melroy.org avatar

@georgengelmann @debounced Ow.. one more thing, adding a add_header to location, will REMOVE all existing headers from the server section. I know, it's insane right? Docs says (and read carefully): There could be several add_header directives. These directives are inherited from the previous level if and only if there are no add_header directives defined on the current level.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • updates
  • testing
  • tech
  • drbboard
  • programming
  • til
  • wanderlust
  • bitcoincash
  • Sacramento
  • All magazines