Changeset 2156 for draft-ietf-httpbis
- Timestamp:
- 24/01/13 11:57:02 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2147 r2156 449 449 } 450 450 @bottom-center { 451 content: "Expires July 2 4, 2013";451 content: "Expires July 28, 2013"; 452 452 } 453 453 @bottom-right { … … 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2013-01-2 0">496 <meta name="dct.issued" scheme="ISO8601" content="2013-01-24"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 522 522 <tr> 523 523 <td class="left">Intended status: Standards Track</td> 524 <td class="right">January 2 0, 2013</td>524 <td class="right">January 24, 2013</td> 525 525 </tr> 526 526 <tr> 527 <td class="left">Expires: July 2 4, 2013</td>527 <td class="left">Expires: July 28, 2013</td> 528 528 <td class="right"></td> 529 529 </tr> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on July 2 4, 2013.</p>555 <p>This Internet-Draft will expire on July 28, 2013.</p> 556 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 557 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 939 939 <h4 id="rfc.section.3.1.1.4"><a href="#rfc.section.3.1.1.4">3.1.1.4</a> <a id="multipart.types" href="#multipart.types">Multipart Types</a></h4> 940 940 <p id="rfc.section.3.1.1.4.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body. 941 All multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and include a boundary parameter as part of the media type value. The message body is itself a protocol element; a sender <em class="bcp14">MUST</em> generate only CRLF to represent line breaks between body -parts.941 All multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and include a boundary parameter as part of the media type value. The message body is itself a protocol element; a sender <em class="bcp14">MUST</em> generate only CRLF to represent line breaks between body parts. 942 942 </p> 943 943 <p id="rfc.section.3.1.1.4.p.2">HTTP message framing does not use the multipart boundary as an indicator of message body length, though it might be used by … … 1168 1168 <tr> 1169 1169 <td class="left">Content-Range</td> 1170 <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 4. 4</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>1170 <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 4.2</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td> 1171 1171 </tr> 1172 1172 <tr> … … 1495 1495 the related resources. 1496 1496 </p> 1497 <p id="rfc.section.4.3.4.p.11">An origin server <em class="bcp14">SHOULD</em> reject any PUT request that contains a <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header field (<a href="p5-range.html#header.content-range" title="Content-Range">Section 4. 4</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), since it might be misinterpreted as partial content (or might be partial content that is being mistakenly PUT as a full1497 <p id="rfc.section.4.3.4.p.11">An origin server <em class="bcp14">SHOULD</em> reject any PUT request that contains a <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header field (<a href="p5-range.html#header.content-range" title="Content-Range">Section 4.2</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), since it might be misinterpreted as partial content (or might be partial content that is being mistakenly PUT as a full 1498 1498 representation). Partial content updates are possible by targeting a separately identified resource with state that overlaps 1499 1499 a portion of the larger resource, or by using a different method that has been specifically defined for partial updates (for … … 2222 2222 <td class="left">206</td> 2223 2223 <td class="left">Partial Content</td> 2224 <td id="status.206" class="left"><a href="p5-range.html#status.206" title="206 Partial Content">Section 4. 2</a> of <a href="#Part5" id="rfc.xref.Part5.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>2224 <td id="status.206" class="left"><a href="p5-range.html#status.206" title="206 Partial Content">Section 4.1</a> of <a href="#Part5" id="rfc.xref.Part5.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td> 2225 2225 </tr> 2226 2226 <tr> … … 2342 2342 <td class="left">416</td> 2343 2343 <td class="left">Range Not Satisfiable</td> 2344 <td id="status.416" class="left"><a href="p5-range.html#status.416" title="416 Range Not Satisfiable">Section 4. 3</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>2344 <td id="status.416" class="left"><a href="p5-range.html#status.416" title="416 Range Not Satisfiable">Section 4.4</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td> 2345 2345 </tr> 2346 2346 <tr> … … 4120 4120 </p> 4121 4121 <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2> 4122 <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body -part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 3.1.1.3</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line4122 <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 3.1.1.3</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line 4123 4123 break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content. 4124 4124 </p> … … 4649 4649 <li><em>Section 3.2</em> <a href="#rfc.xref.Part5.7">5.2</a></li> 4650 4650 <li><em>Section 4</em> <a href="#rfc.xref.Part5.8">6.1</a></li> 4651 <li><em>Section 4. 2</em> <a href="#rfc.xref.Part5.9">6.1</a></li>4652 <li><em>Section 4. 3</em> <a href="#rfc.xref.Part5.10">6.1</a></li>4653 <li><em>Section 4.4</em> <a href="#rfc.xref.Part5. 2">3.3</a>, <a href="#rfc.xref.Part5.5">4.3.4</a></li>4651 <li><em>Section 4.1</em> <a href="#rfc.xref.Part5.9">6.1</a></li> 4652 <li><em>Section 4.2</em> <a href="#rfc.xref.Part5.2">3.3</a>, <a href="#rfc.xref.Part5.5">4.3.4</a></li> 4653 <li><em>Section 4.4</em> <a href="#rfc.xref.Part5.10">6.1</a></li> 4654 4654 <li><em>Appendix A</em> <a href="#rfc.xref.Part5.13">A.6</a></li> 4655 4655 </ul> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2147 r2156 458 458 and include a boundary parameter as part of the media type 459 459 value. The message body is itself a protocol element; a sender &MUST; 460 generate only CRLF to represent line breaks between body -parts.460 generate only CRLF to represent line breaks between body parts. 461 461 </t> 462 462 <t> … … 5698 5698 <section title="Conversion to Canonical Form" anchor="conversion.to.canonical.form"> 5699 5699 <t> 5700 MIME requires that an Internet mail body -part be converted to canonical5700 MIME requires that an Internet mail body part be converted to canonical 5701 5701 form prior to being transferred, as described in <xref target="RFC2049" 5702 5702 x:fmt="of" x:sec="4"/>. <xref target="canonicalization.and.text.defaults"/>
Note: See TracChangeset
for help on using the changeset viewer.