Ignore:
Timestamp:
Mar 9, 2012, 12:46:33 AM (8 years ago)
Author:
fielding@…
Message:

#250 message-body in CONNECT response

Change message body parsing of successful CONNECT responses such that
the tunnel begins immediately after the header block, as implemented in
practice, and any Content-Length or Transfer-Encoding is ignored.

File:
1 edited

Legend:

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

    r1567 r1570  
    15761576   Content-Length, etc.) only indicate what their values would have been
    15771577   if the request method had been GET.
     1578   Successful (2xx) responses to CONNECT switch to tunnel mode instead of
     1579   having a message body.
    15781580   All 1xx (Informational), 204 (No Content), and 304 (Not Modified)
    15791581   responses &MUST-NOT; include a message body.
     
    16931695<t>
    16941696   In the case of a response to a HEAD request, Content-Length indicates
    1695    the size of the payload body (not including any potential transfer-coding)
     1697   the size of the payload body (without any potential transfer-coding)
    16961698   that would have been sent had the request been a GET.
    16971699   In the case of a 304 (Not Modified) response to a GET request,
    1698    Content-Length indicates the size of the payload body (not including
     1700   Content-Length indicates the size of the payload body (without
    16991701   any potential transfer-coding) that would have been sent in a 200 (OK)
    17001702   response.
     1703</t>
     1704<t>
     1705   HTTP's use of Content-Length is significantly different from how it is
     1706   used in MIME, where it is an optional field used only within the
     1707   "message/external-body" media-type.
    17011708</t>
    17021709<t>
     
    17191726   length.
    17201727</t>
    1721 <t>
    1722    HTTP's use of Content-Length is significantly different from how it is
    1723    used in MIME, where it is an optional field used only within the
    1724    "message/external-body" media-type.
    1725 </t>
    17261728</section>
    17271729
     
    17381740     empty line after the header fields, regardless of the header
    17391741     fields present in the message, and thus cannot contain a message body.
     1742    </t></x:lt>
     1743    <x:lt><t>
     1744     Any successful (2xx) response to a CONNECT request implies that the
     1745     connection will become a tunnel immediately after the empty line that
     1746     concludes the header fields.  A client &MUST; ignore any Content-Length
     1747     or Transfer-Encoding header fields received in such a message.
    17401748    </t></x:lt>
    17411749    <x:lt><t>
Note: See TracChangeset for help on using the changeset viewer.