Ignore:
Timestamp:
Jul 4, 2012, 1:44:42 AM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink status codes definitions (5xx range)

Location:
draft-ietf-httpbis/latest
Files:
6 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1708 r1710  
    449449  }
    450450  @bottom-center {
    451        content: "Expires January 4, 2013";
     451       content: "Expires January 5, 2013";
    452452  }
    453453  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2012-07-03">
     493      <meta name="dct.issued" scheme="ISO8601" content="2012-07-04">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: January 4, 2013</td>
     525               <td class="left">Expires: January 5, 2013</td>
    526526               <td class="right">greenbytes</td>
    527527            </tr>
    528528            <tr>
    529529               <td class="left"></td>
    530                <td class="right">July 3, 2012</td>
     530               <td class="right">July 4, 2012</td>
    531531            </tr>
    532532         </tbody>
     
    561561         in progress”.
    562562      </p>
    563       <p>This Internet-Draft will expire on January 4, 2013.</p>
     563      <p>This Internet-Draft will expire on January 5, 2013.</p>
    564564      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    565565      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    10051005      </p>
    10061006      <p id="rfc.section.2.6.p.11">An HTTP server <em class="bcp14">SHOULD</em> send a response version equal to the highest version to which the server is conformant and whose major version is less than
    1007          or equal to the one received in the request. An HTTP server <em class="bcp14">MUST NOT</em> send a version to which it is not conformant. A server <em class="bcp14">MAY</em> send a 505 (HTTP Version Not Supported) response if it cannot send a response using the major version used in the client's
    1008          request.
     1007         or equal to the one received in the request. An HTTP server <em class="bcp14">MUST NOT</em> send a version to which it is not conformant. A server <em class="bcp14">MAY</em> send a <a href="p2-semantics.html#status.505" class="smpl">505 (HTTP Version Not
     1008            Supported)</a> response if it cannot send a response using the major version used in the client's request.
    10091009      </p>
    10101010      <p id="rfc.section.2.6.p.12">An HTTP server <em class="bcp14">MAY</em> send an HTTP/1.0 response to an HTTP/1.0 request if it is known or suspected that the client incorrectly implements the HTTP
     
    11761176      </p>
    11771177      <p id="rfc.section.3.1.1.p.9">HTTP does not place a pre-defined limit on the length of a request-line. A server that receives a method longer than any that
    1178          it implements <em class="bcp14">SHOULD</em> respond with either a 405 (Not Allowed), if it is an origin server, or a 501 (Not Implemented) status code. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 (URI Too Long) status code if the received request-target
     1178         it implements <em class="bcp14">SHOULD</em> respond with either a 405 (Not Allowed), if it is an origin server, or a <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> status code. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 (URI Too Long) status code if the received request-target
    11791179         would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 4.6.12</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
    11801180      </p>
     
    14161416         might be in the form of specific user configuration or by remembering the version of a prior received response. A server <em class="bcp14">MUST NOT</em> send a response containing Transfer-Encoding unless the corresponding request indicates HTTP/1.1 (or later).
    14171417      </p>
    1418       <p id="rfc.section.3.3.1.p.10">A server that receives a request message with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> respond with 501 (Not Implemented) and then close the connection.
     1418      <p id="rfc.section.3.3.1.p.10">A server that receives a request message with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> respond with <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> and then close the connection.
    14191419      </p>
    14201420      <div id="rfc.iref.c.6"></div>
     
    14771477            <p>If a message is received without Transfer-Encoding and with either multiple Content-Length header fields having differing
    14781478               field-values or a single Content-Length header field having an invalid value, then the message framing is invalid and <em class="bcp14">MUST</em> be treated as an error to prevent request or response smuggling. If this is a request message, the server <em class="bcp14">MUST</em> respond with a 400 (Bad Request) status code and then close the connection. If this is a response message received by a proxy,
    1479                the proxy <em class="bcp14">MUST</em> discard the received response, send a 502 (Bad Gateway) status code as its downstream response, and then close the connection.
    1480                If this is a response message received by a user-agent, it <em class="bcp14">MUST</em> be treated as an error by discarding the message and closing the connection.
     1479               the proxy <em class="bcp14">MUST</em> discard the received response, send a <a href="p2-semantics.html#status.502" class="smpl">502 (Bad Gateway)</a> status code as its downstream response, and then close the connection. If this is a response message received by a user-agent,
     1480               it <em class="bcp14">MUST</em> be treated as an error by discarding the message and closing the connection.
    14811481            </p>
    14821482         </li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1708 r1710  
    706706   whose major version is less than or equal to the one received in the
    707707   request.  An HTTP server &MUST-NOT; send a version to which it is not
    708    conformant.  A server &MAY; send a 505 (HTTP
    709    Version Not Supported) response if it cannot send a response using the
     708   conformant.  A server &MAY; send a <x:ref>505 (HTTP Version Not
     709   Supported)</x:ref> response if it cannot send a response using the
    710710   major version used in the client's request.
    711711</t>
     
    10701070   A server that receives a method longer than any that it implements
    10711071   &SHOULD; respond with either a 405 (Not Allowed), if it is an origin
    1072    server, or a 501 (Not Implemented) status code.
     1072   server, or a <x:ref>501 (Not Implemented)</x:ref> status code.
    10731073   A server &MUST; be prepared to receive URIs of unbounded length and
    10741074   respond with the 414 (URI Too Long) status code if the received
     
    15731573<t>
    15741574   A server that receives a request message with a transfer-coding it does
    1575    not understand &SHOULD; respond with 501 (Not Implemented) and then
     1575   not understand &SHOULD; respond with <x:ref>501 (Not Implemented)</x:ref> and then
    15761576   close the connection.
    15771577</t>
     
    16901690     a 400 (Bad Request) status code and then close the connection.
    16911691     If this is a response message received by a proxy, the proxy
    1692      &MUST; discard the received response, send a 502 (Bad Gateway)
     1692     &MUST; discard the received response, send a <x:ref>502 (Bad Gateway)</x:ref>
    16931693     status code as its downstream response, and then close the connection.
    16941694     If this is a response message received by a user-agent, it &MUST; be
     
    41084108  </front>
    41094109  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
    4110   <x:source href="p2-semantics.xml" basename="p2-semantics"/>
     4110  <x:source href="p2-semantics.xml" basename="p2-semantics">
     4111    <x:defines>501 (Not Implemented)</x:defines>
     4112    <x:defines>502 (Bad Gateway)</x:defines>
     4113    <x:defines>505 (HTTP Version Not Supported)</x:defines>
     4114  </x:source>
    41114115</reference>
    41124116
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1708 r1710  
    449449  }
    450450  @bottom-center {
    451        content: "Expires January 4, 2013";
     451       content: "Expires January 5, 2013";
    452452  }
    453453  @bottom-right {
     
    497497      <meta name="dct.creator" content="Reschke, J. F.">
    498498      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    499       <meta name="dct.issued" scheme="ISO8601" content="2012-07-03">
     499      <meta name="dct.issued" scheme="ISO8601" content="2012-07-04">
    500500      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    501501      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation.">
     
    528528            </tr>
    529529            <tr>
    530                <td class="left">Expires: January 4, 2013</td>
     530               <td class="left">Expires: January 5, 2013</td>
    531531               <td class="right">greenbytes</td>
    532532            </tr>
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">July 3, 2012</td>
     535               <td class="right">July 4, 2012</td>
    536536            </tr>
    537537         </tbody>
     
    563563         in progress”.
    564564      </p>
    565       <p>This Internet-Draft will expire on January 4, 2013.</p>
     565      <p>This Internet-Draft will expire on January 5, 2013.</p>
    566566      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    567567      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    891891</pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;9.5</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the
    892892         set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> respond with the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the
    893          resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
    894          and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section&nbsp;2.3</a>.
     893         resource, and <a href="#status.501" class="smpl">501 (Not Implemented)</a> if the method is unrecognized or not implemented by the origin server. The methods GET and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section&nbsp;2.3</a>.
    895894      </p>
    896895      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>
     
    29102909         <li>If the response status code is 100 (Continue) or 101 (Switching Protocols), the response <em class="bcp14">MAY</em> include a Date header field, at the server's option.
    29112910         </li>
    2912          <li>If the response status code conveys a server error, e.g., 500 (Internal Server Error) or 503 (Service Unavailable), and it
    2913             is inconvenient or impossible to generate a valid Date.
     2911         <li>If the response status code conveys a server error, e.g., 500 (Internal Server Error) or <a href="#status.503" class="smpl">503 (Service Unavailable)</a>, and it is inconvenient or impossible to generate a valid Date.
    29142912         </li>
    29152913         <li>If the server does not have a clock that can provide a reasonable approximation of the current time, its responses <em class="bcp14">MUST NOT</em> include a Date header field.
     
    30393037      <div id="rfc.iref.h.17"></div>
    30403038      <h2 id="rfc.section.9.16"><a href="#rfc.section.9.16">9.16</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
    3041       <p id="rfc.section.9.16.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected
    3042          to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing
     3039      <p id="rfc.section.9.16.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service
     3040            Unavailable)</a> response to indicate how long the service is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing
    30433041         the redirected request.
    30443042      </p>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1708 r1710  
    392392   origin server &SHOULD; respond with the status code 405 (Method Not Allowed)
    393393   if the method is known by the origin server but not allowed for the
    394    resource, and 501 (Not Implemented) if the method is
     394   resource, and <x:ref>501 (Not Implemented)</x:ref> if the method is
    395395   unrecognized or not implemented by the origin server. The methods GET
    396396   and HEAD &MUST; be supported by all general-purpose servers. All other
     
    20302030  <iref primary="true" item="501 Not Implemented (status code)" x:for-anchor=""/>
    20312031  <iref primary="true" item="Status Codes" subitem="501 Not Implemented" x:for-anchor=""/>
     2032  <x:anchor-alias value="501 (Not Implemented)"/>
    20322033<t>
    20332034   The server does not support the functionality required to fulfill the
     
    20412042  <iref primary="true" item="502 Bad Gateway (status code)" x:for-anchor=""/>
    20422043  <iref primary="true" item="Status Codes" subitem="502 Bad Gateway" x:for-anchor=""/>
     2044  <x:anchor-alias value="502 (Bad Gateway)"/>
    20432045<t>
    20442046   The server, while acting as a gateway or proxy, received an invalid
     
    20512053  <iref primary="true" item="503 Service Unavailable (status code)" x:for-anchor=""/>
    20522054  <iref primary="true" item="Status Codes" subitem="503 Service Unavailable" x:for-anchor=""/>
     2055  <x:anchor-alias value="503 (Service Unavailable)"/>
    20532056<t>
    20542057   The server is currently unable to handle the request due to a
     
    20742077  <iref primary="true" item="504 Gateway Timeout (status code)" x:for-anchor=""/>
    20752078  <iref primary="true" item="Status Codes" subitem="504 Gateway Timeout" x:for-anchor=""/>
     2079  <x:anchor-alias value="504 (Gateway Timeout)"/>
    20762080<t>
    20772081   The server, while acting as a gateway or proxy, did not receive a
     
    20912095  <iref primary="true" item="505 HTTP Version Not Supported (status code)" x:for-anchor=""/>
    20922096  <iref primary="true" item="Status Codes" subitem="505 HTTP Version Not Supported" x:for-anchor=""/>
     2097  <x:anchor-alias value="505 (HTTP Version Not Supported)"/>
    20932098<t>
    20942099   The server does not support, or refuses to support, the protocol
     
    35163521
    35173522      <t>If the response status code conveys a server error, e.g., 500
    3518          (Internal Server Error) or 503 (Service Unavailable), and it is
    3519          inconvenient or impossible to generate a valid Date.</t>
     3523         (Internal Server Error) or <x:ref>503 (Service Unavailable)</x:ref>,
     3524         and it is inconvenient or impossible to generate a valid Date.</t>
    35203525
    35213526      <t>If the server does not have a clock that can provide a
     
    37923797  <x:anchor-alias value="Retry-After"/>
    37933798<t>
    3794    The header "Retry-After" field can be used with a 503 (Service
    3795    Unavailable) response to indicate how long the service is expected to
     3799   The header "Retry-After" field can be used with a <x:ref>503 (Service
     3800   Unavailable)</x:ref> response to indicate how long the service is expected to
    37963801   be unavailable to the requesting client. This field &MAY; also be used
    37973802   with any 3xx (Redirection) response to indicate the minimum time the
  • draft-ietf-httpbis/latest/p6-cache.html

    r1708 r1710  
    452452  }
    453453  @bottom-center {
    454        content: "Expires January 4, 2013";
     454       content: "Expires January 5, 2013";
    455455  }
    456456  @bottom-right {
     
    494494      <meta name="dct.creator" content="Reschke, J. F.">
    495495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    496       <meta name="dct.issued" scheme="ISO8601" content="2012-07-03">
     496      <meta name="dct.issued" scheme="ISO8601" content="2012-07-04">
    497497      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    498498      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    520520            </tr>
    521521            <tr>
    522                <td class="left">Expires: January 4, 2013</td>
     522               <td class="left">Expires: January 5, 2013</td>
    523523               <td class="right">M. Nottingham, Editor</td>
    524524            </tr>
     
    537537            <tr>
    538538               <td class="left"></td>
    539                <td class="right">July 3, 2012</td>
     539               <td class="right">July 4, 2012</td>
    540540            </tr>
    541541         </tbody>
     
    567567         in progress”.
    568568      </p>
    569       <p>This Internet-Draft will expire on January 4, 2013.</p>
     569      <p>This Internet-Draft will expire on January 5, 2013.</p>
    570570      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    571571      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    13171317      <h4 id="rfc.section.3.2.1.7"><a href="#rfc.section.3.2.1.7">3.2.1.7</a>&nbsp;<a id="cache-request-directive.only-if-cached" href="#cache-request-directive.only-if-cached">only-if-cached</a></h4>
    13181318      <p id="rfc.section.3.2.1.7.p.1">The only-if-cached request directive indicates that the client only wishes to obtain a stored response. If it receives 3ive,
    1319          a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a 504
    1320          (Gateway Timeout) status code. If a group of caches is being operated as a unified system with good internal connectivity,
    1321          a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
     1319         a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a <a href="p2-semantics.html#status.504" class="smpl">504
     1320            (Gateway Timeout)</a> status code. If a group of caches is being operated as a unified system with good internal connectivity, a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches.
    13221321      </p>
    13231322      <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3>
     
    13881387      </p>
    13891388      <p id="rfc.section.3.2.2.5.p.2">The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
    1390          a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a 504 (Gateway Timeout) response.
     1389         a cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if a cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway Timeout)</a> response.
    13911390      </p>
    13921391      <p id="rfc.section.3.2.2.5.p.3">The must-revalidate directive ought to be used by servers if and only if failure to validate a request on the representation
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1708 r1710  
    13611361   wishes to obtain a stored response. If it receives 3ive, a
    13621362   cache &SHOULD; either respond using a stored response that is consistent
    1363    with the other constraints of the request, or respond with a 504
    1364    (Gateway Timeout) status code. If a group of caches is being operated as
     1363   with the other constraints of the request, or respond with a <x:ref>504
     1364   (Gateway Timeout)</x:ref> status code. If a group of caches is being operated as
    13651365   a unified system with good internal connectivity, a member cache &MAY;
    13661366   forward such a request within that group of caches.
     
    15041504   cache &MUST; obey the must-revalidate directive; in particular,
    15051505   if a cache cannot reach the origin server for any reason, it &MUST;
    1506    generate a 504 (Gateway Timeout) response.
     1506   generate a <x:ref>504 (Gateway Timeout)</x:ref> response.
    15071507</t>
    15081508<t>
     
    22872287    </front>
    22882288    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" />
    2289     <x:source basename="p2-semantics" href="p2-semantics.xml" />
     2289    <x:source basename="p2-semantics" href="p2-semantics.xml">
     2290      <x:defines>504 (Gateway Timeout)</x:defines>
     2291    </x:source>
    22902292  </reference>
    22912293
Note: See TracChangeset for help on using the changeset viewer.