Opened 14 years ago
Closed 13 years ago
#172 closed design (fixed)
take over HTTP Upgrade Token Registry
Reported by: | julian.reschke@… | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | unassigned |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
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 (1)
Change History (3)
Changed 13 years ago by julian.reschke@…
comment:1 Changed 13 years ago by julian.reschke@…
comment:2 Changed 13 years ago by mnot@…
- Priority set to normal
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Proposed patch for part 1.