I did figure out that ufw was not allowing udp/443. So it turns out
that wasn't working for any website on that install.
I have another install in AWS that IS working, and it turns out that
when I was seeing the green lightning bolt in firefox, it was one of
those websites, not the ones in my local install. Sometimes I forget
which install covers specific websites.
But even after allowing udp/443, it is still not switching. If I enter
the URL into https://http3check.net/ it does say that http3 works.
On 4/27/23 20:26, Tristan wrote:
As far as I know, the main way it happens is that the browser:
- races H2 and H3 and picks the fastest (then remember it)
- retries on H2 in case of H3 issue (then remember it)
Hmm. The web server is on the local gigabit LAN with the client. Would
that give TCP a significant enough boost that it could beat UDP? What I
learned from forcing quic (see below) seems to support this notion.
> You can try something like that to force it to use H3 and reveal
> whatever issue it might be having:
> chromium-browser --enable-quic
> --origin-to-force-quic-on=your-gitlab-host.com:443
I have chrome, not chromium. Substituting /opt/google/chrome/chrome for
chromium and running it with those options, it DOES do http/3. The
lightning bolt is orange instead of blue.
Thanks,
Shawn
