Changeset 2058 for draft-ietf-httpbis


Ignore:
Timestamp:
27/12/12 16:55:15 (8 years ago)
Author:
fielding@…
Message:

editorial improvements to 5xx status codes; partly addresses #419

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p2-semantics.html

    r2057 r2058  
    26082608      <div id="rfc.iref.74"></div>
    26092609      <h3 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    2610       <p id="rfc.section.6.5.3.p.1">The <dfn>403 (Forbidden)</dfn> status code indicates that the origin server understood the request but refuses to authorize it. A server that wishes to make
    2611          public why the request has been forbidden can describe that reason in the response payload (if any).
    2612       </p>
    2613       <p id="rfc.section.6.5.3.p.2">If authentication credentials were provided in the request, the origin server considers them insufficient to grant access.
    2614          The client <em class="bcp14">SHOULD NOT</em> repeat the request with the same credentials. The client <em class="bcp14">MAY</em> repeat the request with new or different credentials. However, a request might be forbidden for reasons unrelated to the credentials.
     2610      <p id="rfc.section.6.5.3.p.1">The <dfn>403 (Forbidden)</dfn> status code indicates that the server understood the request but refuses to authorize it. A server that wishes to make public
     2611         why the request has been forbidden can describe that reason in the response payload (if any).
     2612      </p>
     2613      <p id="rfc.section.6.5.3.p.2">If authentication credentials were provided in the request, the server considers them insufficient to grant access. The client <em class="bcp14">SHOULD NOT</em> repeat the request with the same credentials. The client <em class="bcp14">MAY</em> repeat the request with new or different credentials. However, a request might be forbidden for reasons unrelated to the credentials.
    26152614      </p>
    26162615      <p id="rfc.section.6.5.3.p.3">An origin server that wishes to "hide" the current existence of a forbidden <a href="#resources" class="smpl">target resource</a>  <em class="bcp14">MAY</em> instead respond with a status code of <a href="#status.404" class="smpl">404 (Not Found)</a>.
    … …  
    27172716      <div id="rfc.iref.75"></div>
    27182717      <h3 id="rfc.section.6.6.1"><a href="#rfc.section.6.6.1">6.6.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    2719       <p id="rfc.section.6.6.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
     2718      <p id="rfc.section.6.6.1.p.1">The <dfn>500 (Internal Server Error)</dfn> status code indicates that the server encountered an unexpected condition which prevented it from fulfilling the request.
     2719      </p>
    27202720      <div id="rfc.iref.75"></div>
    27212721      <h3 id="rfc.section.6.6.2"><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    2722       <p id="rfc.section.6.6.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    2723          does not recognize the request method and is not capable of supporting it for any resource.
     2722      <p id="rfc.section.6.6.2.p.1">The <dfn>501 (Not Implemented)</dfn> status code indicates that the server does not support the functionality required to fulfill the request. This is the appropriate
     2723         response when the server does not recognize the request method and is not capable of supporting it for any resource.
    27242724      </p>
    27252725      <div id="rfc.iref.75"></div>
    27262726      <h3 id="rfc.section.6.6.3"><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    2727       <p id="rfc.section.6.6.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
    2728          to fulfill the request.
     2727      <p id="rfc.section.6.6.3.p.1">The <dfn>502 (Bad Gateway)</dfn> status code indicates that the server, while acting as a gateway or proxy, received an invalid response from an inbound server
     2728         it accessed while attempting to fulfill the request.
    27292729      </p>
    27302730      <div id="rfc.iref.75"></div>
    27312731      <h3 id="rfc.section.6.6.4"><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    2732       <p id="rfc.section.6.6.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
    2733       <p id="rfc.section.6.6.4.p.2">The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the
    2734          delay <em class="bcp14">MAY</em> be indicated in a <a href="#header.retry-after" class="smpl">Retry-After</a> header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;7.1.3</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a <a href="#status.500" class="smpl">500 (Internal
    2735             Server Error)</a> response.
    2736       </p>
    2737       <div class="note" id="rfc.section.6.6.4.p.3">
     2732      <p id="rfc.section.6.6.4.p.1">The <dfn>503 (Service Unavailable)</dfn> status code indicates that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance,
     2733         which will likely be alleviated after some delay. The server <em class="bcp14">MAY</em> send a <a href="#header.retry-after" class="smpl">Retry-After</a> header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;7.1.3</a>) to suggest an appropriate amount of time for the client to wait before retrying the request.
     2734      </p>
     2735      <div class="note" id="rfc.section.6.6.4.p.2">
    27382736         <p> <b>Note:</b> The existence of the 503 status code does not imply that a server has to use it when becoming overloaded. Some servers might
    2739             wish to simply refuse the connection.
     2737            simply refuse the connection.
    27402738         </p>
    27412739      </div>
    27422740      <div id="rfc.iref.75"></div>
    27432741      <h3 id="rfc.section.6.6.5"><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    2744       <p id="rfc.section.6.6.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the
    2745          URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request.
    2746       </p>
    2747       <div class="note" id="rfc.section.6.6.5.p.2">
    2748          <p> <b>Note</b> to implementers: some deployed proxies are known to send <a href="#status.400" class="smpl">400 (Bad Request)</a> or <a href="#status.500" class="smpl">500 (Internal Server
    2749                Error)</a> when DNS lookups time out.
    2750          </p>
    2751       </div>
     2742      <p id="rfc.section.6.6.5.p.1">The <dfn>504 (Gateway Timeout)</dfn> status code indicates that the server, while acting as a gateway or proxy, did not receive a timely response from an upstream
     2743         server it needed to access in order to complete the request.
     2744      </p>
    27522745      <div id="rfc.iref.75"></div>
    27532746      <h3 id="rfc.section.6.6.6"><a href="#rfc.section.6.6.6">6.6.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    2754       <p id="rfc.section.6.6.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
    2755          is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    2756          in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.
     2747      <p id="rfc.section.6.6.6.p.1">The <dfn>505 (HTTP Version Not Supported)</dfn> status code indicates that the server does not support, or refuses to support, the protocol version that was used in the request
     2748         message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the
     2749         client, as described in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, other than with this error message. The server <em class="bcp14">SHOULD</em> generate a representation for the 505 response that describes why that version is not supported and what other protocols are
     2750         supported by that server.
    27572751      </p>
    27582752      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2057 r2058  
    31283128  <x:anchor-alias value="403 (Forbidden)"/>
    31293129<t>
    3130    The <x:dfn>403 (Forbidden)</x:dfn> status code indicates that the origin
     3130   The <x:dfn>403 (Forbidden)</x:dfn> status code indicates that the
    31313131   server understood the request but refuses to authorize it.
    31323132   A server that wishes to make public why the request has been forbidden
    … …  
    31343134</t>
    31353135<t>
    3136    If authentication credentials were provided in the request, the origin
     3136   If authentication credentials were provided in the request, the
    31373137   server considers them insufficient to grant access.
    31383138   The client &SHOULD-NOT; repeat the request with the same credentials.
    … …  
    33783378  <x:anchor-alias value="500 (Internal Server Error)"/>
    33793379<t>
    3380    The server encountered an unexpected condition which prevented it
    3381    from fulfilling the request.
     3380   The <x:dfn>500 (Internal Server Error)</x:dfn> status code indicates that
     3381   the server encountered an unexpected condition which prevented it from
     3382   fulfilling the request.
    33823383</t>
    33833384</section>
    … …  
    33873388  <x:anchor-alias value="501 (Not Implemented)"/>
    33883389<t>
    3389    The server does not support the functionality required to fulfill the
    3390    request. This is the appropriate response when the server does not
    3391    recognize the request method and is not capable of supporting it for
    3392    any resource.
     3390   The <x:dfn>501 (Not Implemented)</x:dfn> status code indicates that the
     3391   server does not support the functionality required to fulfill the request.
     3392   This is the appropriate response when the server does not recognize the
     3393   request method and is not capable of supporting it for any resource.
    33933394</t>
    33943395</section>
    … …  
    33983399  <x:anchor-alias value="502 (Bad Gateway)"/>
    33993400<t>
    3400    The server, while acting as a gateway or proxy, received an invalid
    3401    response from the upstream server it accessed in attempting to
    3402    fulfill the request.
     3401   The <x:dfn>502 (Bad Gateway)</x:dfn> status code indicates that the server,
     3402   while acting as a gateway or proxy, received an invalid response from an
     3403   inbound server it accessed while attempting to fulfill the request.
    34033404</t>
    34043405</section>
    … …  
    34083409  <x:anchor-alias value="503 (Service Unavailable)"/>
    34093410<t>
    3410    The server is currently unable to handle the request due to a
    3411    temporary overloading or maintenance of the server.
    3412 </t>
    3413 <t>
    3414    The implication is that this is a temporary condition which will be
    3415    alleviated after some delay. If known, the length of the delay &MAY; be
    3416    indicated in a <x:ref>Retry-After</x:ref> header field
    3417    (<xref target="header.retry-after"/>). If no Retry-After is given, the
    3418    client &SHOULD; handle the response as it would for a <x:ref>500 (Internal
    3419    Server Error)</x:ref> response.
     3411   The <x:dfn>503 (Service Unavailable)</x:dfn> status code indicates that the
     3412   server is currently unable to handle the request due to a temporary overload
     3413   or scheduled maintenance, which will likely be alleviated after some delay.
     3414   The server &MAY; send a <x:ref>Retry-After</x:ref> header field
     3415   (<xref target="header.retry-after"/>) to suggest an appropriate
     3416   amount of time for the client to wait before retrying the request.
    34203417</t>
    34213418<x:note>
    34223419  <t>
    34233420    &Note; The existence of the 503 status code does not imply that a
    3424     server has to use it when becoming overloaded. Some servers might wish
    3425     to simply refuse the connection.
     3421    server has to use it when becoming overloaded. Some servers might
     3422    simply refuse the connection.
    34263423  </t>
    34273424</x:note>
    … …  
    34323429  <x:anchor-alias value="504 (Gateway Timeout)"/>
    34333430<t>
    3434    The server, while acting as a gateway or proxy, did not receive a
    3435    timely response from the upstream server specified by the URI (e.g.,
    3436    HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed
    3437    to access in attempting to complete the request.
    3438 </t>
    3439 <x:note>
    3440   <t>
    3441     <x:h>Note</x:h> to implementers: some deployed proxies are known to
    3442     send <x:ref>400 (Bad Request)</x:ref> or <x:ref>500 (Internal Server
    3443     Error)</x:ref> when DNS lookups time out.
    3444   </t>
    3445 </x:note>
     3431   The <x:dfn>504 (Gateway Timeout)</x:dfn> status code indicates that the
     3432   server, while acting as a gateway or proxy, did not receive a timely
     3433   response from an upstream server it needed to access in order to
     3434   complete the request.
     3435</t>
    34463436</section>
    34473437
    … …  
    34503440  <x:anchor-alias value="505 (HTTP Version Not Supported)"/>
    34513441<t>
    3452    The server does not support, or refuses to support, the protocol
    3453    version that was used in the request message. The server is
    3454    indicating that it is unable or unwilling to complete the request
    3455    using the same major version as the client, as described in &http-version;,
    3456    other than with this error message. The response &SHOULD; contain
    3457    a representation describing why that version is not supported and what other
     3442   The <x:dfn>505 (HTTP Version Not Supported)</x:dfn> status code indicates
     3443   that the server does not support, or refuses to support, the protocol
     3444   version that was used in the request message. The server is indicating that
     3445   it is unable or unwilling to complete the request using the same major
     3446   version as the client, as described in &http-version;, other than with this
     3447   error message. The server &SHOULD; generate a representation for the 505
     3448   response that describes why that version is not supported and what other
    34583449   protocols are supported by that server.
    34593450</t>
Note: See TracChangeset for help on using the changeset viewer.