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

Definition of authority-form in Messaging must require host:port #806

Closed
royfielding opened this issue Mar 25, 2021 · 0 comments · Fixed by #807
Closed

Definition of authority-form in Messaging must require host:port #806

royfielding opened this issue Mar 25, 2021 · 0 comments · Fixed by #807

Comments

@royfielding
Copy link
Member

In 3.2.3. authority-form it says

The authority-form of request-target is only used for CONNECT requests (Section 9.3.6 of [Semantics]).

authority-form = authority

Whereas it needs to specifically require host:port, as in the definition of CONNECT:

CONNECT uses a special form of request target, unique to this method, consisting of only the host and port number of the tunnel destination, separated by a colon. There is no default port; a client MUST send the port number even if the CONNECT request is based on a URI reference that contains an authority component with an elided port (Section 4.1).

@royfielding royfielding self-assigned this Mar 25, 2021
@royfielding royfielding changed the title Definintion of authority-form in Messaging must require host:port Definition of authority-form in Messaging must require host:port Mar 25, 2021
reschke added a commit that referenced this issue Mar 26, 2021
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.

2 participants