Opened 13 years ago
Closed 12 years ago
#240 closed design (fixed)
Migrate Upgrade details from RFC2817
Reported by: | mnot@… | Owned by: | mnot@… |
---|---|---|---|
Priority: | normal | Milestone: | 13 |
Component: | non-specific | Severity: | Active WG Document |
Keywords: | Cc: |
Description
RFC2817 contains advice and details about how Upgrade works in HTTP; e.g., the 426 status code, and the upgrade token registry. These should be migrated into p1, as discussed in Maastricht.
Attachments (1)
Change History (8)
comment:1 Changed 12 years ago by mnot@…
- Owner set to mnot@…
comment:2 Changed 12 years ago by julian.reschke@…
comment:3 Changed 12 years ago by julian.reschke@…
- Component changed from p1-messaging to non-specific
comment:4 Changed 12 years ago by julian.reschke@…
comment:5 Changed 12 years ago by julian.reschke@…
- Milestone changed from unassigned to 13
- Resolution set to incorporated
- Status changed from new to closed
comment:6 Changed 12 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:7 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
Note: the upgrade token registry was already taken over in draft -07, see issue #172.