* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #172 (closed design: fixed)

Opened 6 years ago

Last modified 5 years ago

take over HTTP Upgrade Token Registry

Reported by: julian.reschke@gmx.de Owned by:
Priority: normal Milestone: unassigned
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin:

Description

Currently the registry prodecure for HTTP Upgrade Tokens is defined in RFC 2817 ("Upgrading to TLS Within HTTP/1.1"), Section 7.2 (<http://tools.ietf.org/html/rfc2817#section-7.2>). This probably should be taken over by Part 1, just as we did with the HTTP status code registry.

Attachments

172.diff (5.4 KB) - added by julian.reschke@gmx.de 5 years ago.
Proposed patch for part 1.

Change History

Changed 5 years ago by julian.reschke@gmx.de

Proposed patch for part 1.

comment:1 Changed 5 years ago by julian.reschke@gmx.de

From [684]:

take over HTTP Upgrade Token Registry (see #172)

comment:2 Changed 5 years ago by mnot@pobox.com

  • Priority set to normal
  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.