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

Ticket #240 (closed design: fixed)

Opened 4 years ago

Last modified 4 years ago

Migrate Upgrade details from RFC2817

Reported by: mnot@pobox.com Owned by: mnot@pobox.com
Priority: normal Milestone: 13
Component: non-specific Severity: Active WG Document
Keywords: Cc:
Origin:

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

240.diff (4.7 KB) - added by julian.reschke@gmx.de 4 years ago.
proposed patch for P1 and P2

Change History

comment:1 Changed 4 years ago by mnot@pobox.com

  • Owner set to mnot@pobox.com

comment:2 Changed 4 years ago by julian.reschke@gmx.de

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

comment:3 Changed 4 years ago by julian.reschke@gmx.de

  • Component changed from p1-messaging to non-specific

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

proposed patch for P1 and P2

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

From [1071]:

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

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

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

comment:6 Changed 4 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:7 Changed 4 years ago by mnot@pobox.com

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