Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP/3 and QUIC filtration feature request #1572

Closed
ammnt opened this issue Dec 18, 2021 · 4 comments
Closed

HTTP/3 and QUIC filtration feature request #1572

ammnt opened this issue Dec 18, 2021 · 4 comments

Comments

@ammnt
Copy link

ammnt commented Dec 18, 2021

Hello,

unfortunately, I could not find any detailed information about the status of HTTP/3 and QUIC filtering support here or on the forum. All I know is that filtration engine are now forcibly downgrading the connection protocol to HTTP/2☹️

So please add the HTTP/3 and QUIC traffic filtering feature in future releases for desktop and mobile applications🙂

Thank you.
Best regards!🎁

@d0x360
Copy link

d0x360 commented Dec 19, 2021

There is DNS quic support if you use Adguard DNS. I don't think any of the other servers can use it yet.

A potential issue with http/3 is ports. If DNS uses a different port than other traffic then "they" will know what's a DNS request and what's regular traffic.

So hopefully they use the same port for both DNS and regular browsing traffic.

It's still really new though and Adguard can't just add it if the system (Android in this case) doesn't support it... I think.

@ammnt
Copy link
Author

ammnt commented Dec 19, 2021

There is DNS quic support if you use Adguard DNS. I don't think any of the other servers can use it yet.

A potential issue with http/3 is ports. If DNS uses a different port than other traffic then "they" will know what's a DNS request and what's regular traffic.

So hopefully they use the same port for both DNS and regular browsing traffic.

It's still really new though and Adguard can't just add it if the system (Android in this case) doesn't support it... I think.

You don't understand what I'm talking about🤦🏻‍♂️ Read how the HTTP/3, QUIC, and DNS-over-QUIC protocols differ. DoQ servers from AdGuard are the first, but not the only ones in the world for a long time - NextDNS also have support too.

HTTP/3 protocol uses the same port 443 as normal HTTPS. No problem here.

And I'm talking not only about Android, but about all the platforms supported by AdGuard applications.

@d0x360
Copy link

d0x360 commented Dec 19, 2021

I do understand, I was just pointing something out, and based on the
protocols I've read what I said is correct.

As for Android I probably should been more clear. "In this case" was just
referring to me because I do... 99.99999% of my web browsing on my phone.
Plus I had just posted 2 issues in the Android section so it was on my mind.

I also know there are more DNS servers that support Quic. I was just
talking about the default ones that are options in Adguard.

Nice facepalm BTW.. I think someone needs to chill. Even if I was 101%
wrong about something this isn't Reddit or the Adguard forums it's Github.

If someone gets something wrong you explain it to them without being
condescending.

@ameshkov
Copy link
Member

Duplicate of #487

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants