Changeset 2353


Ignore:
Timestamp:
Aug 10, 2013, 5:00:48 PM (6 years ago)
Author:
fielding@…
Message:

Restore the ability for 205 responses to be sent with a zero-length chunked body; addresses #491 and related to #88

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r2352 r2353  
    25412541         and then the data entry mechanism is reset for the next entry so that the user can easily initiate another input action.
    25422542      </p>
    2543       <p id="rfc.section.6.3.6.p.3">Since the 205 status code implies that no additional content will be provided in the payload, the server <em class="bcp14">MUST</em> send a message body of zero length. In other words, the server <em class="bcp14">MUST</em> send a "Content-Length: 0" field in a 205 response or close the connection immediately after sending the blank line terminating
    2544          the header section.
     2543      <p id="rfc.section.6.3.6.p.3">Since the 205 status code implies that no additional content will be provided, a server <em class="bcp14">MUST NOT</em> generate a payload in a 205 response. In other words, a server <em class="bcp14">MUST</em> do one of the following for a 205 response: a) indicate a zero-length body for the response by including a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field with a value of 0; b) indicate a zero-length payload for the response by including a <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> header field with a value of chunked and a message body consisting of a single chunk of zero-length; or, c) close the connection
     2544         immediately after sending the blank line terminating the header section.
    25452545      </p>
    25462546      <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
     
    49194919            </li>
    49204920            <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul>
    4921                   <li>TRACE method&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">4.1</a>, <a href="#rfc.iref.t.1"><b>4.3.8</b></a>, <a href="#rfc.xref.TRACE.2">5.1.2</a>, <a href="#rfc.xref.TRACE.3">8.1.3</a>, <a href="#rfc.extref.t.49">B</a>, <a href="#rfc.xref.TRACE.4">B</a>, <a href="#rfc.extref.t.50">B</a></li>
     4921                  <li>TRACE method&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">4.1</a>, <a href="#rfc.iref.t.1"><b>4.3.8</b></a>, <a href="#rfc.xref.TRACE.2">5.1.2</a>, <a href="#rfc.xref.TRACE.3">8.1.3</a>, <a href="#rfc.extref.t.50">B</a>, <a href="#rfc.xref.TRACE.4">B</a>, <a href="#rfc.extref.t.51">B</a></li>
    49224922               </ul>
    49234923            </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2352 r2353  
    29712971<t>
    29722972   Since the 205 status code implies that no additional content will be
    2973    provided in the payload, the server &MUST; send a message body of zero
    2974    length. In other words, the server &MUST; send a "Content-Length: 0" field
    2975    in a 205 response or close the connection immediately after sending the
    2976    blank line terminating the header section.
     2973   provided, a server &MUST-NOT; generate a payload in a 205 response.
     2974   In other words, a server &MUST; do one of the following for a 205 response:
     2975   a) indicate a zero-length body for the response by including a
     2976   <x:ref>Content-Length</x:ref> header field with a value of 0;
     2977   b) indicate a zero-length payload for the response by including a
     2978   <x:ref>Transfer-Encoding</x:ref> header field with a value of chunked and
     2979   a message body consisting of a single chunk of zero-length; or,
     2980   c) close the connection immediately after sending the blank line
     2981   terminating the header section.
    29772982</t>
    29782983</section>
Note: See TracChangeset for help on using the changeset viewer.