Context Navigation

← Previous Ticket
Next Ticket →

#385 closed design (migrated)

Upgrade mechanism

Reported by:	mnot@…	Owned by:
Priority:	normal	Milestone:	unassigned
Component:	http2	Severity:	Active WG Document
Keywords:		Cc:

Description

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).

Change History (3)

comment:1 Changed 7 years ago by mnot@…

Alternate-Protocol mechanism in SPDY:

http://dev.chromium.org/spdy/spdy-protocol/spdy-protocol-draft2#TOC-Server-Advertisement-of-SPDY-through-the-HTTP-Alternate-Protocol-header

comment:2 Changed 7 years ago by mnot@…

Previous study by Chromium for the WebSockets? handshake:

http://www.ietf.org/mail-archive/web/tls/current/msg05593.html

... and the code for the handshake:

http://src.chromium.org/viewvc/chrome/trunk/src/net/websockets/websocket_handshake.cc?view=markup&pathrev=63020

Last edited 7 years ago by mnot@… (previous) (diff)

comment:3 Changed 7 years ago by mnot@…

Resolution set to migrated
Status changed from new to closed

Moved to github issue.

Note: See TracTickets for help on using tickets.

Download in other formats: