Changeset 1038
- Timestamp:
- 19/10/10 09:44:09 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1037 r1038 551 551 <li class="tocline0">4. <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul class="toc"> 552 552 <li class="tocline1">4.1 <a href="#status.code.registry">Status Code Registry</a><ul class="toc"> 553 <li class="tocline1">4.1.1 <a href="# rfc.section.4.1.1">Considerations for New Status Codes</a></li>553 <li class="tocline1">4.1.1 <a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li> 554 554 </ul> 555 555 </li> … … 903 903 <p id="rfc.section.4.1.p.3">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>>. 904 904 </p> 905 <h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a> Considerations for New Status Codes 906 </h3> 905 <h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a> <a id="considerations.for.new.status.codes" href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3> 907 906 <p id="rfc.section.4.1.1.p.1">When it is necessary to express new semantics for a HTTP response that aren't specific to a single application or media type, 908 907 and currently defined status codes are inadequate, a new status code can be registered. … … 2620 2619 <p id="rfc.section.C.13.p.1">Closed issues: </p> 2621 2620 <ul> 2621 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/229">http://tools.ietf.org/wg/httpbis/trac/ticket/229</a>>: "Considerations for new status codes" 2622 </li> 2622 2623 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/230">http://tools.ietf.org/wg/httpbis/trac/ticket/230</a>>: "Considerations for new methods" 2623 2624 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1037 r1038 658 658 </t> 659 659 660 <section title="Considerations for New Status Codes"> 661 662 <t>When it is necessary to express new semantics for a HTTP response that 663 aren't specific to a single application or media type, and currently defined 664 status codes are inadequate, a new status code can be registered.</t> 665 666 <t>New HTTP status codes &MUST; be defined in one of the categories defined 660 <section title="Considerations for New Status Codes" anchor="considerations.for.new.status.codes"> 661 <t> 662 When it is necessary to express new semantics for a HTTP response that 663 aren't specific to a single application or media type, and currently defined 664 status codes are inadequate, a new status code can be registered. 665 </t> 666 <t> 667 New HTTP status codes &MUST; be defined in one of the categories defined 667 668 in <xref target="status.codes"/>. They &MUST-NOT; disallow a response body, 668 669 although they &MAY; mandate a zero-length response body. They &MAY; require 669 the presence of one or more particular HTTP response header(s).</t> 670 671 <t>Likewise, their definitions &MAY; specify that caches are allowed to use 670 the presence of one or more particular HTTP response header(s). 671 </t> 672 <t> 673 Likewise, their definitions &MAY; specify that caches are allowed to use 672 674 heuristics to determine their freshness (see &caching;; by default, it is 673 675 not allowed), and &MAY; define how to determine the resource which they 674 676 carry a representation for (see <xref 675 677 target="identifying.response.associated.with.representation"/>; by default, 676 it is anonymous).</t> 677 678 <t>If there are particular request conditions that produce a response 679 containing the status code (e.g., request headers and/or method(s)), they 680 &SHOULD; be described in detail.</t> 681 682 <t>New HTTP status codes &SHOULD; be registered in a document that isn't 683 specific to a single application or other use of HTTP, so that it's clear that 684 they are not specific to that application or extension.</t> 685 678 it is anonymous). 679 </t> 680 <t> 681 If there are particular request conditions that produce a response 682 containing the status code (e.g., request headers and/or method(s)), they 683 &SHOULD; be described in detail. 684 </t> 685 <t> 686 New HTTP status codes &SHOULD; be registered in a document that isn't 687 specific to a single application or other use of HTTP, so that it's clear that 688 they are not specific to that application or extension. 689 </t> 686 690 </section> 687 691 … … 3886 3890 <list style="symbols"> 3887 3891 <t> 3892 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/229"/>: 3893 "Considerations for new status codes" 3894 </t> 3895 <t> 3888 3896 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/230"/>: 3889 3897 "Considerations for new methods"
Note: See TracChangeset
for help on using the changeset viewer.