Changeset 1911
- Timestamp:
- 22/09/12 07:33:58 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1910 r1911 449 449 } 450 450 @bottom-center { 451 content: "Expires March 2 5, 2013";451 content: "Expires March 26, 2013"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-2 1">494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-22"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 496 496 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: March 2 5, 2013</td>526 <td class="left">Expires: March 26, 2013</td> 527 527 <td class="right">greenbytes</td> 528 528 </tr> 529 529 <tr> 530 530 <td class="left"></td> 531 <td class="right">September 2 1, 2012</td>531 <td class="right">September 22, 2012</td> 532 532 </tr> 533 533 </tbody> … … 556 556 in progress”. 557 557 </p> 558 <p>This Internet-Draft will expire on March 2 5, 2013.</p>558 <p>This Internet-Draft will expire on March 26, 2013.</p> 559 559 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 560 560 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1403 1403 </pre><p id="rfc.section.3.3.2.p.5">A sender <em class="bcp14">MUST NOT</em> send a Content-Length header field in any message that contains a <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> header field. 1404 1404 </p> 1405 <p id="rfc.section.3.3.2.p.6">A server <em class="bcp14">MAY</em> send a Content-Length header field in a response to a HEAD request (<a href="p2-semantics.html#HEAD" title="HEAD">Section 4.3.2</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) in order to indicate the size of the payload body, excluding any potential transfer-coding, that would have been sent had1406 the same request been a GET.1407 </p> 1408 <p id="rfc.section.3.3.2.p.7">A server <em class="bcp14">MAY</em> send a Content-Length header field in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response to a conditional GET request (<a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) in order to indicate the size of the payload body, excluding any potential transfer-coding, that would have been sent in1409 a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response.1405 <p id="rfc.section.3.3.2.p.6">A server <em class="bcp14">MAY</em> send a Content-Length header field in a response to a HEAD request (<a href="p2-semantics.html#HEAD" title="HEAD">Section 4.3.2</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>); a server <em class="bcp14">MUST NOT</em> send Content-Length in such a response unless its field-value equals the decimal number of octets that would have been sent 1406 in the payload body of a response if the same request had used the GET method. 1407 </p> 1408 <p id="rfc.section.3.3.2.p.7">A server <em class="bcp14">MAY</em> send a Content-Length header field in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response to a conditional GET request (<a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>); a server <em class="bcp14">MUST NOT</em> send Content-Length in such a response unless its field-value equals the decimal number of octets that would have been sent 1409 in the payload body of a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request. 1410 1410 </p> 1411 1411 <p id="rfc.section.3.3.2.p.8">A server <em class="bcp14">MUST NOT</em> send a Content-Length header field in any response with a status code of <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> or <a href="p2-semantics.html#status.204" class="smpl">204 (No Content)</a>. A server <em class="bcp14">SHOULD NOT</em> send a Content-Length header field in any <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> response to a CONNECT request (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#Part2" id="rfc.xref.Part2.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). -
draft-ietf-httpbis/latest/p1-messaging.xml
r1910 r1911 1586 1586 <t> 1587 1587 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. 1591 1592 </t> 1592 1593 <t> 1593 1594 A server &MAY; send a Content-Length header field in a 1594 1595 <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. 1598 1600 </t> 1599 1601 <t>
Note: See TracChangeset
for help on using the changeset viewer.