Opened 10 years ago

Closed 9 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)

240.diff​ (4.7 KB) - added by julian.reschke@… 10 years ago.
proposed patch for P1 and P2

Download all attachments as: .zip

Change History (8)

comment:1 Changed 10 years ago by mnot@…

  • Owner set to mnot@…

comment:2 Changed 10 years ago by julian.reschke@…

Note: the upgrade token registry was already taken over in draft -07, see issue #172.

comment:3 Changed 10 years ago by julian.reschke@…

  • Component changed from p1-messaging to non-specific

Changed 10 years ago by julian.reschke@…

proposed patch for P1 and P2

comment:4 Changed 10 years ago by julian.reschke@…

From [1071]:

From 2817: adopt Upgrade semantics for status != 101, plus status code 426 (see #240)

comment:5 Changed 10 years ago by julian.reschke@…

  • Milestone changed from unassigned to 13
  • Resolution set to incorporated
  • Status changed from new to closed

comment:6 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:7 Changed 9 years ago by mnot@…

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