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.

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

Provide an example for escaping "\\" #2665

Closed
tfpauly opened this issue Oct 23, 2023 · 1 comment · Fixed by #2666
Closed

Provide an example for escaping "\\" #2665

tfpauly opened this issue Oct 23, 2023 · 1 comment · Fixed by #2666
Assignees

Comments

@tfpauly
Copy link
Contributor

tfpauly commented Oct 23, 2023

From the list:

At the end of Section 2.1 in https://www.ietf.org/archive/id/draft-ietf-httpbis-alias-proxy-status-05.html, there is this:

It is also possible for a DNS name to include a period character (".") within a label, instead of as a label separator. In this case, the period character MUST be first escaped as ".". Since the "" character itself will be percent-encoded, the name "dot.label.example.com" would be encoded within a next-hop-aliases parameter as follows:

Proxy-Status: proxy.example.net; next-hop="2001:db8::1";
next-hop-aliases="dot%5C.label.example.com,service1.example.com"
Upon parsing this name, "dot%5C.label" MUST be treated as a single label.

Similarly the "" character in a label MUST be escaped as "\". Other uses of "" MUST NOT appear in the label after percent-decoding.

Can that last line be expounded on and clarified? Will a "" character in a label be 'eventually' encoded as "\" or "%5C%5C" or some combination of them?

@tfpauly tfpauly self-assigned this Oct 23, 2023
@tfpauly
Copy link
Contributor Author

tfpauly commented Oct 23, 2023

I think we can add an example for this

tfpauly added a commit that referenced this issue Oct 25, 2023
pmeenan pushed a commit to pmeenan/http-extensions that referenced this issue Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant