fix(client): prefer resolver order always#200
Merged
seanmonstar merged 1 commit intomasterfrom Jun 4, 2025
Merged
Conversation
Member
Author
|
This does mean that hickory-dns needs to figure out how to present a better order, and probably a way for users to configure that order on their system. |
seanmonstar
force-pushed
the
defer-to-resolver-order
branch
from
dd5b31a to
0ed22dd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This was changed in #194, but that change seems to be wrong. The resolver is allowed to express it's priority through the ordering.
See https://datatracker.ietf.org/doc/html/rfc6555#section-6 and curl/curl#16718.
Closes hyperium/hyper#3900