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

Via and default ports #865

Closed
mnot opened this issue Jun 15, 2021 · 5 comments · Fixed by #881
Closed

Via and default ports #865

mnot opened this issue Jun 15, 2021 · 5 comments · Fixed by #881

Comments

@mnot
Copy link
Member

mnot commented Jun 15, 2021

Source: #857

(7.6.3) Via

"If a port is not provided, a recipient MAY interpret that as meaning it was
received on the default TCP port, if any, for the received-protocol."

So if received-protocol is "3", it's a UDP port.

If received-protocol is "1" or "1.1", is the default port 80 or 443? IIUC the
scheme isn't included to determine this.

@mnot mnot added the semantics label Jun 15, 2021
@royfielding
Copy link
Member

It's completely irrelevant to the recipient what port number was used for an upstream intermediary, which is why it says MAY here.

@mnot
Copy link
Member Author

mnot commented Jun 15, 2021

There are two issues here:

  1. The protocol-name doesn't reflect the scheme in use, for HTTPS, it's still 'HTTP'. The practical implication of that is that when HTTPS is used, the port needs to be explicit, even if it's the default for HTTPS. A clarifying note might help here.

  2. HTTP/3 uses UDP, not TCP. Omitting 'TCP' from the MAY requirement might help.

@royfielding
Copy link
Member

This is for Via. HTTPS is not a separate protocol. "https" is a scheme that, among other things, doesn't allow an intermediary to forward HTTP messages until they are beyond the origin secured connection (and hence no longer HTTP/TLS). Whatever the post-TLS origin does to forward its messages via CDN or downstream origins is beyond the scope here.

@royfielding
Copy link
Member

Yes, we can just remove TCP from that sentence.

@martinduke
Copy link

That would be acceptable.

@mnot mnot self-assigned this Jul 1, 2021
mnot added a commit that referenced this issue Jul 2, 2021
@mnot mnot mentioned this issue Jul 2, 2021
@mnot mnot closed this as completed in #881 Jul 3, 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.

3 participants