QUIC oddity (gets h2 the first time around, subsequent retrievals are h3)

Wondering if anyone can explain this. With Chrome and Curl, it seems like the first connect from a restarted client, seems to return data over HTTP/2. Subsequent rounds return HTTP/3. Here’s some output showing it curl --http3 https://noc2.semperen.com/lslr.b64 -I HTTP/2 200 server: nginx/1.

Re: Issue with getting to HTTP/3 or QUIC on first connect

41, Roman Arutyunyan wrote: > > Hi Eric, > >> On 9 Mar 2023, at 10:56, Eric Germann via nginx > <mailto:nginx@nginx.org>> wrote: >> >> I’m having an issue where I (think I) have enabled HTTP3 correctly on my >> nginx server. When I connect to the

Re: Issue with getting to HTTP/3 or QUIC on first connect

Forgot to add, here are the HTTPS [1] records in DNS IN HTTPS 100 . no-default-alpn alpn="h3" IN HTTPS 200 . no-default-alpn alpn="h2" They 100/200 are weights, much like MX records, where the low

Issue with getting to HTTP/3 or QUIC on first connect

I’m having an issue where I (think I) have enabled HTTP3 correctly on my nginx server. When I connect to the server the first time, it indicates HTTP/2 in the logs. If I hit refresh it indicates HTTP/3 from then on. So something is wrong with the configuration of the server to offer headers t

Re: forward 443 requests to correct (?) port

Do you have https: at the front of the URL instead of http:? --- Eric Germann ekgermann {at} semperen {dot} com || ekgermann {at} gmail {dot} com LinkedIn: https://www.linkedin.com/in/ericgermann Medium: https://ekgermann.medium.com

Re: Nginx with OpenSSL 1.1.1n

Compile yourself. I do that and can build it with any OpenSSL version I like. Why? Centos 6 doesn’t update the packages anymore and I’m too lazy to rebuild a reverse proxy. Eric > On Mar 27, 2022, at 10:00, Sergey A. Osokin wrote: > > Hi, > >> On Sun, Mar 27, 2022 at 02:04:10AM -0400, su