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

Ticket #59 (closed editorial: fixed)

Opened 7 years ago

Last modified 6 years ago

Status Code Registry

Reported by: mnot@pobox.com Owned by: julian.reschke@gmx.de
Priority: Milestone: 03
Component: p2-semantics Severity:
Keywords: Cc:
Origin: http://www.w3.org/mid/1171757250.3556.22.camel@henriknordstrom.net

Description

The IANA status code registry should be referred to.

Attachments

i59.diff (18.1 KB) - added by julian.reschke@gmx.de 6 years ago.
proposed change for part 2.
i59.2.diff (18.5 KB) - added by julian.reschke@gmx.de 6 years ago.
proposed change for part 2.

Change History

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

  • Component set to non-specific
  • Milestone set to unassigned

comment:2 Changed 7 years ago by fielding@gbiv.com

  • Milestone changed from unassigned to 02

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

  • Milestone changed from 02 to 03

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

  • Owner set to julian.reschke@gmx.de
  • Component changed from non-specific to p2-semantics

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

From [255]:

Add IANA re-registration of status codes, referencing RFC 2817; todo: consider taking over the registry procedure (related to #59)

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

I think we should also take over the registration procedure, obsoleting RFC2817, Section 7.1.

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

From [256]:

Add missing change log entry (related to #59)

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

proposed change for part 2.

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

proposed change for part 2.

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

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in [262]:

Resolve #59: Take over HTTP Status Code Registry from RFC2817 (closes #59).

Note: See TracTickets for help on using tickets.