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

Jump to bottom

Remove confusing text about ports #1215

Merged
merged 1 commit into from Mar 16, 2018
Merged

Remove confusing text about ports #1215

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 3 additions & 4 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -132,17 +132,16 @@ following header in any response:
Alt-Svc: hq=":50781"
~~~

On receipt of an Alt-Svc header indicating HTTP/QUIC support, a client MAY
On receipt of an Alt-Svc record indicating HTTP/QUIC support, a client MAY
attempt to establish a QUIC connection to the indicated host and port and, if
successful, send HTTP requests using the mapping described in this document.

Connectivity problems (e.g. firewall blocking UDP) can result in QUIC connection
establishment failure, in which case the client SHOULD continue using the
existing connection or try another alternative endpoint offered by the origin.

Servers MAY serve HTTP/QUIC on any UDP port. Servers MUST use the same port
across all IP addresses that serve a single domain, and SHOULD NOT change this
port.
Servers MAY serve HTTP/QUIC on any UDP port, since an alternative always
includes an explicit port.

### QUIC Version Hints {#alt-svc-version-hint}

Expand Down