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

The "mixed-scheme" field is probably needed when you make any request… #242

Closed
wants to merge 2 commits into from
Closed

The "mixed-scheme" field is probably needed when you make any request… #242

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f98d9d6
The "mixed-scheme" field is probably needed when you make any request…
martinthomson Oct 10, 2016
f085c6c
Maybe this is less woolly
martinthomson Oct 12, 2016
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
6 changes: 3 additions & 3 deletions draft-ietf-httpbis-http2-encryption.md
View file
Open in desktop
Expand Up @@ -170,9 +170,9 @@ might use the same connection, because HTTP/2 permits requests for multiple orig
connection.

Because of the risk of server confusion about individual requests' schemes (see {{confuse}}),
clients MUST NOT `http` requests on a connection that would ordinarily be used for `https`
requests, unless the http-opportunistic origin object {{well-known}} for that origin has a
"mixed-scheme" member whose value is "true".
clients MUST NOT reuse a TLS-secured connection for `http` requests, unless the
http-opportunistic origin object {{well-known}} for that origin has a "mixed-scheme" member
with a Boolean value of true.


## The "http-opportunistic" well-known URI {#well-known}
Expand Down