Ignore:
Timestamp:
Jul 5, 2012, 10:06:19 AM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink status code range definitions

File:
1 edited

Legend:

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

    r1726 r1727  
    12871287   HTTP does not place a pre-defined limit on the length of header fields,
    12881288   either in isolation or as a set. A server &MUST; be prepared to receive
    1289    request header fields of unbounded length and respond with a 4xx status
    1290    code if the received header field(s) would be longer than the server wishes
    1291    to handle.
     1289   request header fields of unbounded length and respond with a <x:ref>4xx
     1290   (Client Error)</x:ref> status code if the received header field(s) would be
     1291   longer than the server wishes to handle.
    12921292</t>
    12931293<t>
     
    14821482   Content-Length, etc.) only indicate what their values would have been
    14831483   if the request method had been GET.
    1484    Successful (2xx) responses to CONNECT switch to tunnel mode instead of
     1484   <x:ref>2xx (Successful)</x:ref> responses to CONNECT switch to tunnel mode instead of
    14851485   having a message body.
    1486    All 1xx (Informational), <x:ref>204 (No Content)</x:ref>, and <x:ref>304
     1486   All <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, and <x:ref>304
    14871487   (Not Modified)</x:ref> responses &MUST-NOT; include a message body.
    14881488   All other responses do include a message body, although the body
     
    16491649    </t></x:lt>
    16501650    <x:lt><t>
    1651      Any successful (2xx) response to a CONNECT request implies that the
     1651     Any <x:ref>2xx (Successful)</x:ref> response to a CONNECT request implies that the
    16521652     connection will become a tunnel immediately after the empty line that
    16531653     concludes the header fields.  A client &MUST; ignore any Content-Length
     
    26692669   order sent on that connection and &MUST; associate each received response
    26702670   message to the highest ordered request that has not yet received a final
    2671    (non-1xx) response.
     2671   (non-<x:ref>1xx</x:ref>) response.
    26722672</t>
    26732673</section>
     
    27612761   An HTTP/1.1 server that does not support persistent connections &MUST;
    27622762   include the "close" connection option in every response message that
    2763    does not have a 1xx (Informational) status code.
     2763   does not have a <x:ref>1xx (Informational)</x:ref> status code.
    27642764</t>
    27652765</section>
     
    31943194        client and did not include an Expect header field with
    31953195        the "100-continue" expectation. This requirement overrides the
    3196         general rule for forwarding of 1xx responses (see &status-1xx;).
     3196        general rule for forwarding of <x:ref>1xx</x:ref> responses (see &status-1xx;).
    31973197    </t>
    31983198  </list>
     
    32723272   The Upgrade header field cannot be used to indicate a switch to a
    32733273   protocol on a different connection. For that purpose, it is more
    3274    appropriate to use a 3xx redirection response (&status-3xx;).
     3274   appropriate to use a <x:ref>3xx (Redirection)</x:ref> response (&status-3xx;).
    32753275</t>
    32763276<t>
     
    41094109  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
    41104110  <x:source href="p2-semantics.xml" basename="p2-semantics">
     4111    <x:defines>1xx (Informational)</x:defines>
     4112    <x:defines>1xx</x:defines>
    41114113    <x:defines>100 (Continue)</x:defines>
    41124114    <x:defines>101 (Switching Protocols)</x:defines>
     4115    <x:defines>2xx (Successful)</x:defines>
     4116    <x:defines>2xx</x:defines>
    41134117    <x:defines>200 (OK)</x:defines>
    41144118    <x:defines>204 (No Content)</x:defines>
     4119    <x:defines>3xx (Redirection)</x:defines>
     4120    <x:defines>3xx</x:defines>
    41154121    <x:defines>301 (Moved Permanently)</x:defines>
     4122    <x:defines>4xx (Client Error)</x:defines>
     4123    <x:defines>4xx</x:defines>
    41164124    <x:defines>400 (Bad Request)</x:defines>
    41174125    <x:defines>405 (Method Not Allowed)</x:defines>
Note: See TracChangeset for help on using the changeset viewer.