AdguardTeam
QUIC troubles, part 2
https://github.com/AdguardTeam/CoreLibs/issues/1822
It hasn't been resolved:
@DavidOsipov Hello! HTTP/3 filtering in Edge won't work until they allow user certificates for HTTP/3. This is true for all Chrome-based browsers. This can't be fixed on AdGuard's side.
I tried this one, but it still doesn't work.
I see that it's on the Edge side, but could Adguard team create a ticket for a feature request for MS Edge and link it to this issue?
- The issue covers all Chrome-based browsers, which is >80 worldwide, so more than 80 of your customers suffer from inability of using QUIC in their web browsers.
- Linking the issue would let you and other premium users to easily track progress
- Other premium users would consider this issue before prolonging their licenses
I believe that the problem is in Chromium code base, and there's a ticket about non-unified certificate verification between QUIC and TLS. We wait for resolution since they are actively working on that ticket past weeks. We will send separate reports if situation is not changed.
To test HTTP/3 filtering in Chromium-based browser today, you may force using quic for particular domain by using --origin-to-force-quic-on=quic.nginx.org:443 command line option. This option is also supports wildcards, however, * can not be used because it will break every non-HTTP/3 site :(
I believe that the problem is in Chromium code base, and there's a ticket about non-unified certificate verification between QUIC and TLS. We wait for resolution since they are actively working on that ticket past weeks. We will send separate reports if situation is not changed.
To test HTTP/3 filtering in Chromium-based browser today, you may force using quic for particular domain by using
--origin-to-force-quic-on=quic.nginx.org:443command line option. This option is also supports wildcards, however,*can not be used because it will break every non-HTTP/3 site :(
Could you please follow up on this issue?
