-
Notifications
You must be signed in to change notification settings - Fork 42
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
Comments
|
It's completely irrelevant to the recipient what port number was used for an upstream intermediary, which is why it says MAY here. |
|
There are two issues here:
|
|
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. |
|
Yes, we can just remove TCP from that sentence. |
|
That would be acceptable. |
Source: #857
The text was updated successfully, but these errors were encountered: