Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Upgrade Mechanism #1

Closed
mnot opened this Issue Feb 7, 2013 · 2 comments

Comments

Projects
None yet
1 participant
Owner

mnot commented Feb 7, 2013

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 Feb 7, 2013

@mnot mnot reopened this Feb 7, 2013

This was referenced Feb 20, 2013

Owner

mnot commented Feb 27, 2013

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
Owner

mnot commented Mar 5, 2014

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

@mnot mnot closed this Mar 5, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment