Ignore:
Timestamp:
Sep 22, 2012, 12:33:58 AM (7 years ago)
Author:
fielding@…
Message:

Further to [1908], require that a Content-Length accurately reflect the
size of "what would have been" the payload body if it is sent in a
HEAD response or 304 response.

File:
1 edited

Legend:

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

    r1910 r1911  
    15861586<t>
    15871587   A server &MAY; send a Content-Length header field in a response to a HEAD
    1588    request (&HEAD;) in order to indicate the size of the payload body,
    1589    excluding any potential transfer-coding, that would have been sent had the
    1590    same request been a GET.
     1588   request (&HEAD;); a server &MUST-NOT; send Content-Length in such a
     1589   response unless its field-value equals the decimal number of octets that
     1590   would have been sent in the payload body of a response if the same
     1591   request had used the GET method.
    15911592</t>
    15921593<t>
    15931594   A server &MAY; send a Content-Length header field in a
    15941595   <x:ref>304 (Not Modified)</x:ref> response to a conditional GET request
    1595    (&status-304;) in order to indicate the size of the payload body,
    1596    excluding any potential transfer-coding, that would have been sent in a
    1597    <x:ref>200 (OK)</x:ref> response.
     1596   (&status-304;); a server &MUST-NOT; send Content-Length in such a
     1597   response unless its field-value equals the decimal number of octets that
     1598   would have been sent in the payload body of a <x:ref>200 (OK)</x:ref>
     1599   response to the same request.
    15981600</t>
    15991601<t>
Note: See TracChangeset for help on using the changeset viewer.