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.

Sign up for GitHub

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

Add reference to RFC3493 #2668

Merged
merged 1 commit into from
Oct 25, 2023
Merged

Add reference to RFC3493 #2668

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions draft-ietf-httpbis-alias-proxy-status.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,9 +165,9 @@ In order to include the `next-hop-aliases` parameter, a proxy needs to have acce
of alias names and canonical names received in CNAME records.

Implementations ought to note that the full chain of names might not be available in common DNS
resolution APIs, such as `getaddrinfo`. `getaddrinfo` does have an option for `AI_CANONNAME`,
but this will only return the last name in the chain (the canonical name), not the alias
names.
resolution APIs, such as `getaddrinfo`. `getaddrinfo` does have an option for `AI_CANONNAME`
({{Section 6.1 of ?RFC3493}}), but this will only return the last name in the chain
(the canonical name), not the alias names.

An implementation MAY include incomplete information in the `next-hop-aliases` parameter to accommodate cases where it is unable to include the full chain, such as only including the canonical name if the implementation can only use `getaddrinfo` as described above.

Expand Down