Changeset 133
- Timestamp:
- 01/01/08 16:07:37 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r132 r133 632 632 <p id="rfc.section.1.1.p.3">Practical information systems require more functionality than simple retrieval, including search, front-end update, and annotation. 633 633 HTTP allows an open-ended set of methods and headers that indicate the purpose of a request <a href="#RFC2324" id="rfc.xref.RFC2324.1"><cite title="Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)">[RFC2324]</cite></a>. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) <a href="#RFC1630" id="rfc.xref.RFC1630.1"><cite title="Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web">[RFC1630]</cite></a>, as a location (URL) <a href="#RFC1738" id="rfc.xref.RFC1738.1"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> or name (URN) <a href="#RFC1737" id="rfc.xref.RFC1737.1"><cite title="Functional Requirements for Uniform Resource Names">[RFC1737]</cite></a>, for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by 634 Internet mail <a href="#RFC 822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> as defined by the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>.634 Internet mail <a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a> as defined by the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>. 635 635 </p> 636 636 <p id="rfc.section.1.1.p.4">HTTP is also used as a generic protocol for communication between user agents and proxies/gateways to other Internet systems, … … 1048 1048 Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 1049 1049 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 1050 </pre><p id="rfc.section.3.3.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a> (an update to <a href="#RFC822" id="rfc.xref.RFC822. 2"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>). The other formats are described here only for compatibility with obsolete implementations. HTTP/1.1 clients and servers1050 </pre><p id="rfc.section.3.3.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a> (an update to <a href="#RFC822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>). The other formats are described here only for compatibility with obsolete implementations. HTTP/1.1 clients and servers 1051 1051 that parse the date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix B</a> for further information. 1052 1052 </p> … … 1173 1173 <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p> 1174 1174 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.51"></span> HTTP-message = Request | Response ; HTTP/1.1 messages 1175 </pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section 5</a>) and Response (<a href="#response" title="Response">Section 6</a>) messages use the generic message format of <a href="#RFC 822" id="rfc.xref.RFC822.3"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header1175 </pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section 5</a>) and Response (<a href="#response" title="Response">Section 6</a>) messages use the generic message format of <a href="#RFC2822" id="rfc.xref.RFC2822.2"><cite title="Internet Message Format">[RFC2822]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header 1176 1176 fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header 1177 1177 fields, and possibly a message-body. … … 1189 1189 </p> 1190 1190 <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a id="message.headers" href="#message.headers">Message Headers</a></h2> 1191 <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section 4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc 822#section-3.1">Section 3.1</a> of <a href="#RFC822" id="rfc.xref.RFC822.4"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The1191 <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section 4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc2822#section-2.1">Section 2.1</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.3"><cite title="Internet Message Format">[RFC2822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The 1192 1192 field value <em class="bcp14">MAY</em> be preceded by any amount of LWS, though a single SP is preferred. Header fields can be extended over multiple lines by preceding 1193 1193 each extra line with at least one SP or HT. Applications ought to follow "common form", where one is known or indicated, when … … 1640 1640 <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a> <a id="header.date" href="#header.date">Date</a></h2> 1641 1641 <p id="rfc.section.8.3.p.1">The Date general-header field represents the date and time at which the message was originated, having the same semantics 1642 as orig-date in <a href="#RFC822" id="rfc.xref.RFC822. 5"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section 3.3.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.1642 as orig-date in <a href="#RFC822" id="rfc.xref.RFC822.2"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section 3.3.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 1643 1643 </p> 1644 1644 <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.73"></span> Date = "Date" ":" HTTP-date … … 1803 1803 <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a> <a id="header.via" href="#header.via">Via</a></h2> 1804 1804 <p id="rfc.section.8.9.p.1">The Via general-header field <em class="bcp14">MUST</em> be used by gateways and proxies to indicate the intermediate protocols and recipients between the user agent and the server 1805 on requests, and between the origin server and the client on responses. It is analogous to the "Received" field of <a href="#RFC 822" id="rfc.xref.RFC822.6"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities1805 on requests, and between the origin server and the client on responses. It is analogous to the "Received" field of <a href="#RFC2822" id="rfc.xref.RFC2822.4"><cite title="Internet Message Format">[RFC2822]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities 1806 1806 of all senders along the request/response chain. 1807 1807 </p> … … 1911 1911 <p id="rfc.section.10.6.p.1">They exist. They are hard to defend against. Research continues. Beware.</p> 1912 1912 <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 1913 <p id="rfc.section.11.p.1">This specification makes heavy use of the augmented BNF and generic constructs defined by David H. Crocker for <a href="#RFC822 " id="rfc.xref.RFC822.7"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Similarly, it reuses many of the definitions provided by Nathaniel Borenstein and Ned Freed for MIME <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>. We hope that their inclusion in this specification will help reduce past confusion over the relationship between HTTP and1913 <p id="rfc.section.11.p.1">This specification makes heavy use of the augmented BNF and generic constructs defined by David H. Crocker for <a href="#RFC822ABNF" id="rfc.xref.RFC822ABNF.2"><cite title="Standard for the format of ARPA Internet text messages">[RFC822ABNF]</cite></a>. Similarly, it reuses many of the definitions provided by Nathaniel Borenstein and Ned Freed for MIME <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>. We hope that their inclusion in this specification will help reduce past confusion over the relationship between HTTP and 1914 1914 Internet mail message formats. 1915 1915 </p> … … 1998 1998 <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References 1999 1999 </h2> 2000 <table summary="Informative References"> 2000 <table summary="Informative References"> 2001 2001 <tr> 2002 2002 <td class="reference"><b id="Nie1997">[Nie1997]</b></td> … … 2075 2075 <td class="reference"><b id="RFC2821">[RFC2821]</b></td> 2076 2076 <td class="top"><a title="AT&T Laboratories">Klensin, J.</a>, “<a href="http://tools.ietf.org/html/rfc2821">Simple Mail Transfer Protocol</a>”, RFC 2821, April 2001. 2077 </td> 2078 </tr> 2079 <tr> 2080 <td class="reference"><b id="RFC2822">[RFC2822]</b></td> 2081 <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc2822">Internet Message Format</a>”, RFC 2822, April 2001. 2077 2082 </td> 2078 2083 </tr> … … 2619 2624 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">E.1</a></li> 2620 2625 <li class="indline1"><em>RFC2821</em> <a class="iref" href="#rfc.xref.RFC2821.1">1.1</a>, <a class="iref" href="#RFC2821"><b>12.2</b></a></li> 2626 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#rfc.xref.RFC2822.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2822.2">4.1</a>, <a class="iref" href="#rfc.xref.RFC2822.3">4.2</a>, <a class="iref" href="#rfc.xref.RFC2822.4">8.9</a>, <a class="iref" href="#RFC2822"><b>12.2</b></a><ul class="ind"> 2627 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.RFC2822.3">4.2</a></li> 2628 </ul> 2629 </li> 2621 2630 <li class="indline1"><em>RFC3977</em> <a class="iref" href="#rfc.xref.RFC3977.1">1.1</a>, <a class="iref" href="#RFC3977"><b>12.2</b></a></li> 2622 2631 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#RFC4288"><b>12.3</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li> 2623 <li class="indline1"><em>RFC822</em> <a class="iref" href="#rfc.xref.RFC822.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC822.2">3.3.1</a>, <a class="iref" href="#rfc.xref.RFC822.3">4.1</a>, <a class="iref" href="#rfc.xref.RFC822.4">4.2</a>, <a class="iref" href="#rfc.xref.RFC822.5">8.3</a>, <a class="iref" href="#rfc.xref.RFC822.6">8.9</a>, <a class="iref" href="#rfc.xref.RFC822.7">11</a>, <a class="iref" href="#RFC822"><b>12.2</b></a><ul class="ind"> 2624 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.RFC822.4">4.2</a></li> 2625 </ul> 2626 </li> 2627 <li class="indline1"><em>RFC822ABNF</em> <a class="iref" href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a class="iref" href="#RFC822ABNF"><b>12.1</b></a></li> 2632 <li class="indline1"><em>RFC822</em> <a class="iref" href="#rfc.xref.RFC822.1">3.3.1</a>, <a class="iref" href="#rfc.xref.RFC822.2">8.3</a>, <a class="iref" href="#RFC822"><b>12.2</b></a></li> 2633 <li class="indline1"><em>RFC822ABNF</em> <a class="iref" href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC822ABNF.2">11</a>, <a class="iref" href="#RFC822ABNF"><b>12.1</b></a></li> 2628 2634 <li class="indline1"><em>RFC959</em> <a class="iref" href="#rfc.xref.RFC959.1">1.1</a>, <a class="iref" href="#RFC959"><b>12.2</b></a></li> 2629 2635 </ul> -
draft-ietf-httpbis/latest/p1-messaging.xml
r132 r133 257 257 (URL) <xref target="RFC1738"/> or name (URN) <xref target="RFC1737"/>, for indicating the resource to which a 258 258 method is to be applied. Messages are passed in a format similar to 259 that used by Internet mail <xref target="RFC 822"/> as defined by the Multipurpose259 that used by Internet mail <xref target="RFC2822"/> as defined by the Multipurpose 260 260 Internet Mail Extensions (MIME) <xref target="RFC2045"/>. 261 261 </t> … … 1314 1314 <t> 1315 1315 Request (<xref target="request"/>) and Response (<xref target="response"/>) messages use the generic 1316 message format of <xref target="RFC 822"/> for transferring entities (the payload1316 message format of <xref target="RFC2822"/> for transferring entities (the payload 1317 1317 of the message). Both types of message consist of a start-line, zero 1318 1318 or more header fields (also known as "headers"), an empty line (i.e., … … 1346 1346 request-header (&request-header-fields;), response-header (&response-header-fields;), and 1347 1347 entity-header (&entity-header-fields;) fields, follow the same generic format as 1348 that given in <xref target="RFC 822" x:fmt="of" x:sec="3.1"/>. Each header field consists1348 that given in <xref target="RFC2822" x:fmt="of" x:sec="2.1"/>. Each header field consists 1349 1349 of a name followed by a colon (":") and the field value. Field names 1350 1350 are case-insensitive. The field value &MAY; be preceded by any amount … … 2617 2617 agent and the server on requests, and between the origin server and 2618 2618 the client on responses. It is analogous to the "Received" field of 2619 <xref target="RFC 822"/> and is intended to be used for tracking message forwards,2619 <xref target="RFC2822"/> and is intended to be used for tracking message forwards, 2620 2620 avoiding request loops, and identifying the protocol capabilities of 2621 2621 all senders along the request/response chain. … … 2851 2851 <t> 2852 2852 This specification makes heavy use of the augmented BNF and generic 2853 constructs defined by David H. Crocker for <xref target="RFC822 "/>. Similarly, it2853 constructs defined by David H. Crocker for <xref target="RFC822ABNF"/>. Similarly, it 2854 2854 reuses many of the definitions provided by Nathaniel Borenstein and 2855 2855 Ned Freed for MIME <xref target="RFC2045"/>. We hope that their inclusion in this … … 3466 3466 </front> 3467 3467 <seriesInfo name="RFC" value="2821"/> 3468 </reference> 3469 3470 <reference anchor="RFC2822"> 3471 <front> 3472 <title>Internet Message Format</title> 3473 <author initials="P." surname="Resnick" fullname="P. Resnick"> 3474 <organization>QUALCOMM Incorporated</organization> 3475 </author> 3476 <date year="2001" month="April"/> 3477 </front> 3478 <seriesInfo name="RFC" value="2822"/> 3468 3479 </reference> 3469 3480 -
draft-ietf-httpbis/latest/p2-semantics.html
r130 r133 1393 1393 <div id="rfc.iref.h.4"></div> 1394 1394 <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a> <a id="header.from" href="#header.from">From</a></h2> 1395 <p id="rfc.section.10.3.p.1">The From request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href=" #RFC822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> as updated by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>:1395 <p id="rfc.section.10.3.p.1">The From request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc2822#section-3.4">Section 3.4</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a>: 1396 1396 </p> 1397 1397 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.16"></span> From = "From" ":" mailbox … … 1595 1595 <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References 1596 1596 </h2> 1597 <table summary="Informative References"> 1597 <table summary="Informative References"> 1598 1598 <tr> 1599 1599 <td class="reference"><b id="Luo1998">[Luo1998]</b></td> … … 1602 1602 </tr> 1603 1603 <tr> 1604 <td class="reference"><b id="RFC1123">[RFC1123]</b></td>1605 <td class="top"><a title="University of Southern California (USC), Information Sciences Institute">Braden, R.</a>, “<a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts - Application and Support</a>”, STD 3, RFC 1123, October 1989.1606 </td>1607 </tr>1608 <tr>1609 1604 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 1610 1605 <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC 1945, May 1996. … … 1622 1617 </tr> 1623 1618 <tr> 1624 <td class="reference"><b id="RFC 822">[RFC822]</b></td>1625 <td class="top"> <a title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD 11, RFC 822, August 1982.1619 <td class="reference"><b id="RFC2822">[RFC2822]</b></td> 1620 <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc2822">Internet Message Format</a>”, RFC 2822, April 2001. 1626 1621 </td> 1627 1622 </tr> … … 1951 1946 <li class="indline1">Referer header <a class="iref" href="#rfc.xref.header.referer.1">4</a>, <a class="iref" href="#rfc.iref.r.1"><b>10.6</b></a></li> 1952 1947 <li class="indline1">Retry-After header <a class="iref" href="#rfc.xref.header.retry-after.1">6</a>, <a class="iref" href="#rfc.iref.r.2"><b>10.7</b></a></li> 1953 <li class="indline1"><em>RFC1123</em> <a class="iref" href="#rfc.xref.RFC1123.1">10.3</a>, <a class="iref" href="#RFC1123"><b>14.2</b></a></li>1954 1948 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#rfc.xref.RFC1945.1">9.3.3</a>, <a class="iref" href="#RFC1945"><b>14.2</b></a></li> 1955 1949 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">9.3.3</a>, <a class="iref" href="#rfc.xref.RFC2068.2">9.3.6</a>, <a class="iref" href="#RFC2068"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li> 1956 1950 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14.1</b></a></li> 1957 1951 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">B.1</a></li> 1958 <li class="indline1"><em>RFC822</em> <a class="iref" href="#rfc.xref.RFC822.1">10.3</a>, <a class="iref" href="#RFC822"><b>14.2</b></a></li> 1952 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#rfc.xref.RFC2822.1">10.3</a>, <a class="iref" href="#RFC2822"><b>14.2</b></a><ul class="ind"> 1953 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.RFC2822.1">10.3</a></li> 1954 </ul> 1955 </li> 1959 1956 </ul> 1960 1957 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r130 r133 1736 1736 e-mail address for the human user who controls the requesting user 1737 1737 agent. The address &SHOULD; be machine-usable, as defined by "mailbox" 1738 in <xref target="RFC822"/> as updated by <xref target="RFC1123"/>:1738 in <xref x:sec="3.4" x:fmt="of" target="RFC2822"/>: 1739 1739 </t> 1740 1740 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="From"/> … … 2375 2375 </reference> 2376 2376 2377 <reference anchor="RFC822">2378 <front>2379 <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>2380 <author initials="D.H." surname="Crocker" fullname="David H. Crocker">2381 <organization>University of Delaware, Dept. of Electrical Engineering</organization>2382 <address><email>DCrocker@UDel-Relay</email></address>2383 </author>2384 <date month="August" day="13" year="1982"/>2385 </front>2386 <seriesInfo name="STD" value="11"/>2387 <seriesInfo name="RFC" value="822"/>2388 </reference>2389 2390 <reference anchor="RFC1123">2391 <front>2392 <title>Requirements for Internet Hosts - Application and Support</title>2393 <author initials="R." surname="Braden" fullname="Robert Braden">2394 <organization>University of Southern California (USC), Information Sciences Institute</organization>2395 <address><email>Braden@ISI.EDU</email></address>2396 </author>2397 <date month="October" year="1989"/>2398 </front>2399 <seriesInfo name="STD" value="3"/>2400 <seriesInfo name="RFC" value="1123"/>2401 </reference>2402 2403 2377 <reference anchor="RFC1945"> 2404 2378 <front> … … 2483 2457 </front> 2484 2458 <seriesInfo name="RFC" value="2616"/> 2459 </reference> 2460 2461 <reference anchor="RFC2822"> 2462 <front> 2463 <title>Internet Message Format</title> 2464 <author initials="P." surname="Resnick" fullname="P. Resnick"> 2465 <organization>QUALCOMM Incorporated</organization> 2466 </author> 2467 <date year="2001" month="April"/> 2468 </front> 2469 <seriesInfo name="RFC" value="2822"/> 2485 2470 </reference> 2486 2471 -
draft-ietf-httpbis/latest/p3-payload.html
r132 r133 1335 1335 </tr> 1336 1336 <tr> 1337 <td class="reference"><b id="RFC2822">[RFC2822]</b></td> 1338 <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc2822">Internet Message Format</a>”, RFC 2822, April 2001. 1339 </td> 1340 </tr> 1341 <tr> 1337 1342 <td class="reference"><b id="RFC3629">[RFC3629]</b></td> 1338 1343 <td class="top"><a title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, RFC 3629, STD 63, November 2003. 1339 </td>1340 </tr>1341 <tr>1342 <td class="reference"><b id="RFC822">[RFC822]</b></td>1343 <td class="top"><a title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD 11, RFC 822, August 1982.1344 1344 </td> 1345 1345 </tr> … … 1371 1371 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 1372 1372 <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="differences.between.http.entities.and.rfc.2045.entities" href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a></h1> 1373 <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC 822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow entities to be transmitted in an open variety of representations and with extensible mechanisms. However, RFC 20451373 <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow entities to be transmitted in an open variety of representations and with extensible mechanisms. However, RFC 2045 1374 1374 discusses mail, and HTTP has a few features that are different from those described in RFC 2045. These differences were carefully 1375 1375 chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types, to make date … … 1698 1698 <li class="indline1"><em>RFC2557</em> <a class="iref" href="#RFC2557"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2557.2">C.1</a></li> 1699 1699 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li> 1700 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#RFC2822"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2822.1">A</a></li> 1700 1701 <li class="indline1"><em>RFC3629</em> <a class="iref" href="#rfc.xref.RFC3629.1">2.1</a>, <a class="iref" href="#RFC3629"><b>9.2</b></a></li> 1701 1702 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC4288.2">2.3</a>, <a class="iref" href="#RFC4288"><b>9.3</b></a></li> 1702 <li class="indline1"><em>RFC822</em> <a class="iref" href="#RFC822"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC822.1">A</a></li>1703 1703 </ul> 1704 1704 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r132 r133 1842 1842 <references title="Informative References"> 1843 1843 1844 <reference anchor="RFC822">1845 <front>1846 <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>1847 <author initials="D.H." surname="Crocker" fullname="David H. Crocker">1848 <organization>University of Delaware, Dept. of Electrical Engineering</organization>1849 <address><email>DCrocker@UDel-Relay</email></address>1850 </author>1851 <date month="August" day="13" year="1982"/>1852 </front>1853 <seriesInfo name="STD" value="11"/>1854 <seriesInfo name="RFC" value="822"/>1855 </reference>1856 1857 1844 <reference anchor="RFC1806"> 1858 1845 <front> … … 1871 1858 </reference> 1872 1859 1860 <reference anchor="RFC1945"> 1861 <front> 1862 <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title> 1863 <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee"> 1864 <organization>MIT, Laboratory for Computer Science</organization> 1865 <address><email>timbl@w3.org</email></address> 1866 </author> 1867 <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding"> 1868 <organization>University of California, Irvine, Department of Information and Computer Science</organization> 1869 <address><email>fielding@ics.uci.edu</email></address> 1870 </author> 1871 <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen"> 1872 <organization>W3 Consortium, MIT Laboratory for Computer Science</organization> 1873 <address><email>frystyk@w3.org</email></address> 1874 </author> 1875 <date month="May" year="1996"/> 1876 </front> 1877 <seriesInfo name="RFC" value="1945"/> 1878 </reference> 1879 1880 <reference anchor="RFC2049"> 1881 <front> 1882 <title abbrev="MIME Conformance">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</title> 1883 <author initials="N." surname="Freed" fullname="Ned Freed"> 1884 <organization>Innosoft International, Inc.</organization> 1885 <address><email>ned@innosoft.com</email></address> 1886 </author> 1887 <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein"> 1888 <organization>First Virtual Holdings</organization> 1889 <address><email>nsb@nsb.fv.com</email></address> 1890 </author> 1891 <date month="November" year="1996"/> 1892 </front> 1893 <seriesInfo name="RFC" value="2049"/> 1894 </reference> 1895 1873 1896 <reference anchor="RFC2068"> 1874 1897 <front> … … 1899 1922 </reference> 1900 1923 1901 <reference anchor="RFC1945">1902 <front>1903 <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>1904 <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">1905 <organization>MIT, Laboratory for Computer Science</organization>1906 <address><email>timbl@w3.org</email></address>1907 </author>1908 <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">1909 <organization>University of California, Irvine, Department of Information and Computer Science</organization>1910 <address><email>fielding@ics.uci.edu</email></address>1911 </author>1912 <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">1913 <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>1914 <address><email>frystyk@w3.org</email></address>1915 </author>1916 <date month="May" year="1996"/>1917 </front>1918 <seriesInfo name="RFC" value="1945"/>1919 </reference>1920 1921 <reference anchor="RFC2049">1922 <front>1923 <title abbrev="MIME Conformance">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</title>1924 <author initials="N." surname="Freed" fullname="Ned Freed">1925 <organization>Innosoft International, Inc.</organization>1926 <address><email>ned@innosoft.com</email></address>1927 </author>1928 <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">1929 <organization>First Virtual Holdings</organization>1930 <address><email>nsb@nsb.fv.com</email></address>1931 </author>1932 <date month="November" year="1996"/>1933 </front>1934 <seriesInfo name="RFC" value="2049"/>1935 </reference>1936 1937 1924 <reference anchor="RFC2076"> 1938 1925 <front> … … 2050 2037 </front> 2051 2038 <seriesInfo name="RFC" value="2616"/> 2039 </reference> 2040 2041 <reference anchor="RFC2822"> 2042 <front> 2043 <title>Internet Message Format</title> 2044 <author initials="P." surname="Resnick" fullname="P. Resnick"> 2045 <organization>QUALCOMM Incorporated</organization> 2046 </author> 2047 <date year="2001" month="April"/> 2048 </front> 2049 <seriesInfo name="RFC" value="2822"/> 2052 2050 </reference> 2053 2051 … … 2094 2092 <section title="Differences Between HTTP Entities and RFC 2045 Entities" anchor="differences.between.http.entities.and.rfc.2045.entities"> 2095 2093 <t> 2096 HTTP/1.1 uses many of the constructs defined for Internet Mail (<xref target="RFC 822"/>) and the Multipurpose Internet Mail Extensions (MIME <xref target="RFC2045"/>) to2094 HTTP/1.1 uses many of the constructs defined for Internet Mail (<xref target="RFC2822"/>) and the Multipurpose Internet Mail Extensions (MIME <xref target="RFC2045"/>) to 2097 2095 allow entities to be transmitted in an open variety of 2098 2096 representations and with extensible mechanisms. However, RFC 2045
Note: See TracChangeset
for help on using the changeset viewer.