Ignore:
Timestamp:
Oct 18, 2010, 11:12:43 PM (9 years ago)
Author:
mnot@…
Message:

Explain considerations for new status codes; addresses #229.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1034 r1035  
    507507
    508508  <t>HTTP methods &SHOULD; be registered in a document that isn't specific to
    509   an application or other use of HTTP, so that it's clear that they are not
    510   specific to that application or extension.</t>
     509  a single application or other use of HTTP, so that it's clear that they are
     510  not specific to that application or extension.</t>
    511511
    512512</section>
     
    652652  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>.
    653653</t>
     654
     655<section title="Considerations for New Status Codes">
     656 
     657   <t>When it is necessary to express new semantics for a HTTP response that
     658  aren't specific to a single application or media type, and currently defined
     659  status codes are inadequate, a new status code can be registered.</t>
     660 
     661   <t>New HTTP status codes &MUST; be defined in one of the categories defined
     662   in <xref target="status.codes"/>. They &MUST-NOT; disallow a response body,
     663   although they &MAY; mandate a zero-length response body. They &MAY; require
     664   the presence of one or more particular HTTP response header(s).</t>
     665 
     666   <t>Likewise, their definitions &MAY; specify that caches are allowed to use
     667   heuristics to determine their freshness (see &caching;; by default, it is
     668   not allowed), and &MAY; define how to determine the resource which they
     669   carry a representation for (see <xref
     670   target="identifying.response.associated.with.representation"/>; by default,
     671   it is anonymous).</t>
     672 
     673   <t>If there are particular request conditions that produce a response
     674  containing the status code (e.g., request headers and/or method(s)), they
     675  &SHOULD; be described in detail.</t>
     676 
     677   <t>New HTTP status codes &SHOULD; be registered in a document that isn't
     678  specific to a single application or other use of HTTP, so that it's clear that
     679  they are not specific to that application or extension.</t>
     680 
     681</section>
     682
    654683</section>
    655684
Note: See TracChangeset for help on using the changeset viewer.