Ignore:
Timestamp:
07/05/14 15:47:43 (6 years ago)
Author:
julian.reschke@…
Message:

expand a few status code mentions (#553)

File:
1 edited

Legend:

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

    r2654 r2655  
    13791379   status code depending on the result of processing the POST request;
    13801380   almost all of the status codes defined by this specification might be
    1381    received in a response to POST (the exceptions being 206, 304, and 416).
     1381   received in a response to POST (the exceptions being <x:ref>206 (Partial Content)</x:ref>,
     1382   <x:ref>304 (Not Modified)</x:ref>, and <x:ref>416 (Range Not Satisfiable)</x:ref>).
    13821383</t>
    13831384<t>
     
    16231624   CONNECT is intended only for use in requests to a proxy.
    16241625   An origin server that receives a CONNECT request for itself &MAY;
    1625    respond with a <x:ref>2xx</x:ref> status code to indicate that a connection
     1626   respond with a <x:ref>2xx (Successful)</x:ref> status code to indicate that a connection
    16261627   is established.  However, most origin servers do not implement CONNECT.
    16271628</t>
     
    19571958    &Note; The Expect header field was added after the original publication of
    19581959    HTTP/1.1 <xref target="RFC2068"/> as both the means to request an interim
    1959     100 response and the general mechanism for indicating must-understand
     1960    <x:ref>100 (Continue)</x:ref> response and the general mechanism for indicating must-understand
    19601961    extensions. However, the extension mechanism has not been used by clients
    19611962    and the must-understand requirements have not been implemented by many
     
    26162617   For example, if an unrecognized status code of 471 is received by a client,
    26172618   the client can assume that there was something wrong with its request and
    2618    treat the response as if it had received a 400 status code. The response
     2619   treat the response as if it had received a <x:ref>400 (Bad Request)</x:ref> status code. The response
    26192620   message will usually contain a representation that explains the status.
    26202621</t>
     
    40864087</t>
    40874088<t>
    4088    For example, an ETag header field in a 201 response communicates the
     4089   For example, an ETag header field in a <x:ref>201 (Created)</x:ref> response communicates the
    40894090   entity-tag of the newly created resource's representation, so that it can
    40904091   be used in later conditional requests to prevent the "lost update"
     
    51955196    <x:defines>206</x:defines>
    51965197    <x:defines>206 (Partial Content)</x:defines>
     5198    <x:defines>416</x:defines>
     5199    <x:defines>416 (Range Not Satisfiable)</x:defines>
    51975200    <x:defines>Content-Range</x:defines>
    51985201    <x:defines>If-Range</x:defines>
Note: See TracChangeset for help on using the changeset viewer.