Clarify SRV origin selection documentation#13419
Open
bneradt wants to merge 1 commit into
Open
Conversation
randall
reviewed
Jul 22, 2026
randall
reviewed
Jul 22, 2026
SRV origin discovery is difficult to find outside the records reference, and the existing port description contradicts Traffic Server behavior. This can cause operators to miss the feature or constrain SRV records unnecessarily. This documents lookup-name construction, SRV target and port selection, fallback behavior, HostDB caching, and the feature's use from remap replacement URLs. Fixes: apache#12440
bneradt
force-pushed
the
docs-srv-origin-selection
branch
from
July 22, 2026 02:11
b012788 to
e99b9ed
Compare
Contributor
Author
|
[approve ci] |
randall
approved these changes
Jul 22, 2026
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
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.
SRV origin discovery is difficult to find outside the records
reference, and the existing port description contradicts Traffic Server
behavior. This can cause operators to miss the feature or constrain SRV
records unnecessarily.
This documents lookup-name construction, SRV target and port selection,
fallback behavior, HostDB caching, and the feature's use from remap
replacement URLs.
Fixes: #12440