Changeset 133 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 01/01/08 16:07:37 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
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
Note: See TracChangeset
for help on using the changeset viewer.