Sergey Fionov

It was DDoS protection that triggered. The temporary workaround may be to add `search.shopping.naver.com` to HTTPS exclusions

@Alex-302 Domain does not exist, and with `https://example.org/?dn=maphuahin.com&pid=9POT3387I&pbsubid=f3de3781-7342-44ad-8fd6-4839cebfd6d7&noads=http` it works as expected.

Ok, I see. works with https:// but http:// does not match.

@Alex-302 It is not related to QUIC protocol. In your log, you can see that browser immediately fallbacks to HTTP/2. Seems to be caused by blocking video ads. For example...

@Alex-302 Closing this issue because it is caused by ad blocking. You may try to use another set of rules which does not break it on the desktop.

Another report from user with Wireguard in "user mode" + AG in root proxy mode - he experiences problems with IPv6 filtering.

@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 believe that the problem is in Chromium code base, and there's a ticket about [non-unified certificate verification between QUIC and TLS](https://bugs.chromium.org/p/chromium/issues/detail?id=848277). We wait for resolution since they are actively...

Since most of the sites has ECDSA certs, it is good thing to generate ECDSA cert for such sites. This will speed things up. We can also change root certificate...

@bropines New DnsLibs should arrive in one of the next nightlies