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

Ticket #213 (closed design: fixed)

Opened 6 years ago

Last modified 5 years ago

What is the value space of HTTP status codes?

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


p1 defines HTTP status codes as "a 3-digit integer result code" with the following value space:

The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role. There are 5 values for the first digit:

  • 1xx: Informational - Request received, continuing process
  • 2xx: Success - The action was successfully received, understood, and accepted
  • 3xx: Redirection - Further action must be taken in order to complete the request
  • 4xx: Client Error - The request contains bad syntax or cannot be fulfilled
  • 5xx: Server Error - The server failed to fulfill an apparently valid request

The BNF, however, allows other values;

Status-Code = 3DIGIT

IANA has asked what the status of codes is outside of this range; e.g., is a 0xx status code reserved, unregistered, or just not allowed? Likewise for 6xx (used by some implementations for local status codes) and upwards.

Also, should the value space be defined in p1 or p2?

Change History

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

From [982]:

initial version of content-disposition ID derived from draft-reschke-rfc2183-in-http-03 (see #213)

comment:2 Changed 5 years ago by mnot@pobox.com

p2-semantics now says:

New HTTP status codes are required to fall under one of the categories defined in Section 8.

As per #229.

I think this makes it clear that codes outside those ranges are disallowed (at least for registration purposes).

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

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

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

(the change actually happened in [1035])

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

  • Milestone changed from unassigned to 13
Note: See TracTickets for help on using tickets.