AdguardTeam
Protocol connection fallback to HTTP/2 when filtration is enabled
Please answer the following questions for yourself before submitting an issue
- [x] Filters were updated before reproducing an issue
- [x] I checked the knowledge base and found no answer
- [x] I checked to make sure that this issue has not already been filed
AdGuard version
7.20.2 (4988) (CL 1.17.108, DL 2.5.51 )
Browser version
Firefox 137.0.2 (64-разрядный)
OS version
Windows 11 Pro 24H2 Сборка 26100.3775
Traffic filtering
- [x] yes, I do
Ad Blocking
No response
Privacy
No response
Social
No response
Annoyances
No response
Security
No response
Other
No response
Language-specific
No response
Which DNS server do you use?
DNS protection disabled
DNS protocol
DNS-over-HTTPS
Custom DNS
I have a site which support HTTP/3. And it works only when filtration is disabled:
I added this to site to exclusions in "Filters" section and "HTTPS filtration" section with IP. Also HTTP/3 filtration and DoH3 are enabled too in advanced options. But I still have:
What is wrong?
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
Steps to reproduce:
- Enable filtration
- Go to any site which support HTTP/3
- Check the protocol in browser
Expected Behavior
Actual Behavior
Screenshots
Screenshot 1
Additional Information
No response
@ammnt Hi! We recommend installing the latest nightly version. Please let us know if the issue persists.
@ammnt based on our tests, this behavior appears to be fixed in this version. If the issue persists, please send us the logs so we can investigate further.
@StanleyLynn, unfortunately I have the same behavior. The logs and configuration export has been sent just now to [email protected] and [email protected]. Please take a look
@ammnt Thank you for the information and logs. We're working on a fix, and it will be included in one of the future versions.
@StanleyLynn, can you confirm please that this is a real bug? And please explain what is the reason why this happened. Thank you
firefox network.http.http3.disable_when_third_party_roots_found → false
Thanks for your answer! I've changed this parameter, but I have the same behavior as before:
I don't know what happened, but after the last update (7.21.1 (5081)) it works perfect at least: