Ignore:
Timestamp:
Jul 6, 2012, 7:48:51 AM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink status codes definitions (P2)

File:
1 edited

Legend:

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

    r1734 r1735  
    14841484   <x:ref>2xx (Successful)</x:ref> responses to CONNECT switch to tunnel mode instead of
    14851485   having a message body.
    1486    All <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, and <x:ref>304
    1487    (Not Modified)</x:ref> responses &MUST-NOT; include a message body.
     1486   All <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, and
     1487   <x:ref>304 (Not Modified)</x:ref> responses &MUST-NOT; include a message body.
    14881488   All other responses do include a message body, although the body
    14891489   &MAY; be of zero length. (See &status-codes; and &status-304;.)
     
    16431643  <list style="numbers">
    16441644    <x:lt><t>
    1645      Any response to a HEAD request and any response with a status
    1646      code of 100-199, 204, or <x:ref>304 (Not Modified)</x:ref> is always
     1645     Any response to a HEAD request and any response with a
     1646     <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, or
     1647     <x:ref>304 (Not Modified)</x:ref> status code is always
    16471648     terminated by the first empty line after the header fields, regardless of
    16481649     the header fields present in the message, and thus cannot contain a
     
    26622663   to the order in which requests are made on the same connection.
    26632664   More than one response message per request only occurs when one or more
    2664    informational responses (1xx, see &status-1xx;) precede a final response
     2665   informational responses (<x:ref>1xx</x:ref>, see &status-1xx;) precede a final response
    26652666   to the same request.
    26662667</t>
Note: See TracChangeset for help on using the changeset viewer.