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

RFC8164 is exemplary #4223

Merged
merged 1 commit into from
Oct 15, 2020
Merged

RFC8164 is exemplary #4223

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions draft-ietf-quic-http.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -362,11 +362,10 @@ to identify other services that are also authoritative and that might be
reachable over HTTP/3.

Prior to making requests for an origin whose scheme is not "https", the client
MUST ensure the server is willing to serve that scheme. If the client intends
to make requests for an origin whose scheme is "http", this means that it MUST
obtain a valid `http-opportunistic` response for the origin as described in
{{!RFC8164}} prior to making any such requests. Other schemes might define
other mechanisms.
MUST ensure the server is willing to serve that scheme. For origins whose scheme
is "http", an experimental method to accomplish this is described in
{{?RFC8164}}. Other mechanisms might be defined for various schemes in the
future.


## Connection Establishment {#connection-establishment}
Expand Down