-
Notifications
You must be signed in to change notification settings - Fork 143
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
QUIC disabled for dns.google and www.google.com #1873
Comments
3 tasks
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
Nov 12, 2021
3 tasks
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
Nov 12, 2021
This diff changes code the release/3.11 branch to ensure we're not using dns.google and www.google.com over HTTP3. As documented in ooni/probe#1873, since this morning (approx) these services do not support HTTP3 anymore. (I didn't bother with checking whether this issue affects _other_ Google services; I just limited my analysis to the services that we were using as part of testing.) This patch WILL require forward porting to the master branch.
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
Nov 12, 2021
This commit forward ports dedd84f. Original commit message: - - - This diff changes code the release/3.11 branch to ensure we're not using dns.google and www.google.com over HTTP3. As documented in ooni/probe#1873, since this morning (approx) these services do not support HTTP3 anymore. (I didn't bother with checking whether this issue affects _other_ Google services; I just limited my analysis to the services that we were using as part of testing.) This patch WILL require forward porting to the master branch.
3 tasks
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
Nov 12, 2021
… (#594) This commit forward ports dedd84f. Original commit message: - - - This diff changes code the release/3.11 branch to ensure we're not using dns.google and www.google.com over HTTP3. As documented in ooni/probe#1873, since this morning (approx) these services do not support HTTP3 anymore. (I didn't bother with checking whether this issue affects _other_ Google services; I just limited my analysis to the services that we were using as part of testing.) This patch WILL require forward porting to the master branch.
Fixed by ooni/probe-cli#593 and ooni/probe-cli#594. Follow-up issue: #1874. The original problem has been addressed, so we can close the issue. |
ainghazal
pushed a commit
to ainghazal/probe-cli
that referenced
this issue
Mar 8, 2022
…i#593) (ooni#594) This commit forward ports cb92ecf39bcd51e614fe2a89b47d8cc3eeb569a2. Original commit message: - - - This diff changes code the release/3.11 branch to ensure we're not using dns.google and www.google.com over HTTP3. As documented in ooni/probe#1873, since this morning (approx) these services do not support HTTP3 anymore. (I didn't bother with checking whether this issue affects _other_ Google services; I just limited my analysis to the services that we were using as part of testing.) This patch WILL require forward porting to the master branch.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have many integration tests that use 8.8.8.8, dns.google, www.google.com with QUIC. This morning I noticed many of them started failing (see, e.g., https://github.com/ooni/probe-cli/runs/4188573018). What's happening?
(Cc: @fortuna)
I also noticed that
www.google.com
anddns.google
do not advertise QUIC using theAlt-Svc
header anymore. See:and
In both cases,
alt-svc
value isclear
.I don't think this is just an issue with our client implementation, but I'll compile
quiche-client
and see what happens with it.So, here are some runs using
quiche-client
(I compiled cloudflare/quiche@3ea9bf4):I see similar errors and successes when using
miniooni
and forcing HTTP3. See below:So, clearly timeouts. Here are the corresponding OONI reports:
cloudflare-dns.com
www.cloudflare.com
www.google.com
dns.google
This fact is quite annoying for us, because we have many tests that are failing. I'll try to figure out if I can quickly modify those tests to use cloudflare services instead of Google services.
The text was updated successfully, but these errors were encountered: