Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Upgrade Mechanism #1

Closed
mnot opened this Issue · 2 comments

1 participant

@mnot
Owner

This is a tracking ticket for issues related to the mechanism for upgrading from HTTP/1.x.

As per our charter, this is:

A negotiation mechanism that is capable of not only choosing between HTTP/1.x and HTTP/2.x, but also for bindings of HTTP URLs to other transports (for example).

@mnot mnot closed this
@mnot mnot reopened this
This was referenced
@mnot
Owner

Current plan:

  1. HTTPS URLs

    • use NPN (or its replacement); uses OPAQUE TOKEN to negotiate
    • then send magic + SETTINGS
  2. HTTP URLs
    a. existing connection / new connection without context
    - Upgrade Dance; uses OPAQUE TOKEN to negotiate
    - then send magic + SETTINGS

    b. new connection with context (e.g., because you used DNS hint, header hint, prior knowledge)

    • NO upgrade dance
    • first send magic + SETTINGS
@mnot
Owner

Discussions seem to have converged; closing this tracking issue (although more specific issues may still be open).

@mnot mnot closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.