Opened 14 years ago

Closed 13 years ago

#59 closed editorial (fixed)

Status Code Registry

Reported by: mnot@… Owned by: julian.reschke@…
Priority: Milestone: 03
Component: p2-semantics Severity:
Keywords: Cc:

Description

The IANA status code registry should be referred to.

Attachments (2)

i59.diff​ (18.1 KB) - added by julian.reschke@… 13 years ago.
proposed change for part 2.
i59.2.diff​ (18.5 KB) - added by julian.reschke@… 13 years ago.
proposed change for part 2.

Download all attachments as: .zip

Change History (10)

comment:1 Changed 13 years ago by mnot@…

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

comment:2 Changed 13 years ago by fielding@…

  • Milestone changed from unassigned to 02

comment:3 Changed 13 years ago by mnot@…

  • Milestone changed from 02 to 03

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

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

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

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 13 years ago by julian.reschke@…

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

comment:7 Changed 13 years ago by julian.reschke@…

From [256]:

Add missing change log entry (related to #59)

Changed 13 years ago by julian.reschke@…

proposed change for part 2.

Changed 13 years ago by julian.reschke@…

proposed change for part 2.

comment:8 Changed 13 years ago by julian.reschke@…

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

Fixed in [262]:

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

Note: See TracTickets for help on using tickets.