-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
HTTPS RR from DoH is ignored #16966
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
Comments
icing
added a commit
to icing/curl
that referenced
this issue
Apr 4, 2025
Stupidly, the HTTPSRR check on the record's target was not working as it used the wrong index on the NUL byte if the target was not NULL. refs curl#16966
@pkropachev, oh my. there was a silly mistake when checking the target of the httpsrr record. Fixed in #16968. Would be nice if you could verify. Thanks! |
@icing, fix works for me! Thanks! HTTPS RR is advertised by DoH for HTTP server1.
In result,
HTTPS RR is not advertised by DoH for HTTP server2.
So,
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I did this
Hello team!
I use DoH to resolve the HTTP server.
HTTP server supports
h3
protocol, DNS and DoH provides corresponding resource record.But by some reason
curl
usesh2
protocol to work with HTTP server. It looks likecurl
ignores HTTPS RR from DoH.According to Wireshark,
curl
sends query for HTTPS type and gets response from DoH.I expected the following
curl
handles response from DoH and uses the corresponding HTTP protocol.curl/libcurl version
curl 8.13.1-DEV
operating system
Ubuntu 20.04.6
The text was updated successfully, but these errors were encountered: