Changeset 458 for draft-ietf-httpbis/latest
- Timestamp:
- 28/02/09 19:39:48 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r457 r458 672 672 MIME-like message payloads for flexible interaction with network-based hypertext information systems. HTTP relies upon the 673 673 Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate resource targets and relationships between resources. Messages are passed in a format similar to that used by 674 Internet mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</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> (see <a href="p3-payload.html#differences.between.http.entities.and.rfc.2045.entities" title=" ERROR: Anchor 'differences.between.http.entities.and.rfc.2045.entities' not found in p3-payload.xml.">Appendix ERROR: Anchor 'differences.between.http.entities.and.rfc.2045.entities' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages).674 Internet mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</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> (see <a href="p3-payload.html#differences.between.http.entities.and.rfc.2045.entities" title="Differences Between HTTP Entities and RFC 2045 Entities">Appendix A</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages). 675 675 </p> 676 676 <p id="rfc.section.1.p.2">HTTP is a generic interface protocol for informations systems. It is designed to hide the details of how a service is implemented … … 733 733 </pre><p id="rfc.section.1.2.1.p.6">For compatibility with legacy list rules, recipients <em class="bcp14">SHOULD</em> accept empty list elements. In other words, consumers would follow the list productions: 734 734 </p> 735 <div id="rfc.figure.u.4"></div><pre class="text"> #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ]736 737 1#element => *( "," OWS ) element *( OWS "," [ OWS element ] )735 <div id="rfc.figure.u.4"></div><pre class="text"> #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ] 736 737 1#element => *( "," OWS ) element *( OWS "," [ OWS element ] ) 738 738 </pre><p id="rfc.section.1.2.1.p.8"> <a href="#collected.abnf" title="Collected ABNF">Appendix D</a> shows the collected ABNF, with the list rules expanded as explained above. 739 739 </p> … … 741 741 <div id="rule.CRLF"> 742 742 <p id="rfc.section.1.2.2.p.1"> HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix A</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described 743 in <a href="p3-payload.html#media.types" title=" ERROR: Anchor 'media.types' not found in p3-payload.xml.">Appendix ERROR: Anchor 'media.types' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.743 in <a href="p3-payload.html#media.types" title="Media Types">Section 2.3</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 744 744 </p> 745 745 </div> … … 793 793 <div id="rfc.figure.u.9"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">request-header</a> = <request-header, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>> 794 794 <a href="#abnf.dependencies" class="smpl">response-header</a> = <response-header, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>> 795 </pre><div id="rfc.figure.u.10"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">entity-body</a> = <entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="E RROR: Anchor 'entity.body' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.body' not found in p3-payload.xml.</a>>796 <a href="#abnf.dependencies" class="smpl">entity-header</a> = <entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="E RROR: Anchor 'entity.header.fields' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.</a>>795 </pre><div id="rfc.figure.u.10"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">entity-body</a> = <entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="Entity Body">Section 3.2</a>> 796 <a href="#abnf.dependencies" class="smpl">entity-header</a> = <entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>> 797 797 </pre><div id="rfc.figure.u.11"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 15.4</a>> 798 798 <a href="#abnf.dependencies" class="smpl">Pragma</a> = <Pragma, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 15.4</a>> … … 970 970 <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a> <a id="full.date" href="#full.date">Full Date</a></h3> 971 971 <p id="rfc.section.3.2.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p> 972 <div id="rfc.figure.u.19"></div><pre class="text"> 973 974 972 <div id="rfc.figure.u.19"></div><pre class="text"> Sun, 06 Nov 1994 08:49:37 GMT ; RFC 1123 973 Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 974 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 975 975 </pre><p id="rfc.section.3.2.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>. The other formats are described here only for compatibility with obsolete implementations. HTTP/1.1 clients and servers 976 976 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 A</a> for further information. … … 1063 1063 </p> 1064 1064 <p id="rfc.section.3.3.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry 1065 contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section 3.3.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title=" ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).1066 </p> 1067 <p id="rfc.section.3.3.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title=" ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).1065 contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section 3.3.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1066 </p> 1067 <p id="rfc.section.3.3.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 1068 1068 </p> 1069 1069 <p id="rfc.section.3.3.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client. … … 1137 1137 <a href="#product.tokens" class="smpl">product-version</a> = <a href="#rule.token.separators" class="smpl">token</a> 1138 1138 </pre><p id="rfc.section.3.4.p.3">Examples:</p> 1139 <div id="rfc.figure.u.26"></div><pre class="text"> 1140 1139 <div id="rfc.figure.u.26"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1140 Server: Apache/0.8.4 1141 1141 </pre><p id="rfc.section.3.4.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token character <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value). 1142 1142 </p> 1143 1143 <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a> <a id="quality.values" href="#quality.values">Quality Values</a></h2> 1144 <p id="rfc.section.3.5.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 8.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title=" ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight1144 <p id="rfc.section.3.5.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 8.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight 1145 1145 is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has 1146 1146 a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. … … 1315 1315 *(( <a href="#general.header.fields" class="smpl">general-header</a> ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1316 1316 / <a href="#abnf.dependencies" class="smpl">request-header</a> ; <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a> 1317 / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> ) ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="E RROR: Anchor 'entity.header.fields' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.</a>1317 / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> ) ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a> 1318 1318 <a href="#core.rules" class="smpl">CRLF</a> 1319 1319 [ <a href="#message.body" class="smpl">message-body</a> ] ; <a href="#message.body" title="Message Body">Section 4.3</a> … … 1408 1408 *(( <a href="#general.header.fields" class="smpl">general-header</a> ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1409 1409 / <a href="#abnf.dependencies" class="smpl">response-header</a> ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a> 1410 / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> ) ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="E RROR: Anchor 'entity.header.fields' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.</a>1410 / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> ) ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a> 1411 1411 <a href="#core.rules" class="smpl">CRLF</a> 1412 1412 [ <a href="#message.body" class="smpl">message-body</a> ] ; <a href="#message.body" title="Message Body">Section 4.3</a> … … 2539 2539 </p> 2540 2540 <dl class="empty"> 2541 <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title=" ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).2541 <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses). 2542 2542 </dd> 2543 2543 </dl> … … 2546 2546 <dl class="empty"> 2547 2547 <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of 2548 entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="E RROR: Anchor 'entity' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.2548 entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 3</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 2549 2549 </dd> 2550 2550 </dl> … … 2607 2607 </p> 2608 2608 <dl class="empty"> 2609 <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title=" ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.2609 <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status. 2610 2610 </dd> 2611 2611 </dl> … … 3224 3224 </li> 3225 3225 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">3.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.5</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.10">A</a>, <a class="iref" href="#rfc.xref.Part3.11">B.3</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a><ul class="ind"> 3226 <li class="indline1"><em> Appendix </em> <a class="iref" href="#rfc.xref.Part3.1">1</a></li>3227 <li class="indline1"><em> Appendix</em> <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li>3228 <li class="indline1"><em> Appendix </em> <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li>3229 <li class="indline1"><em> Appendix </em> <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li>3230 <li class="indline1"><em> Appendix </em> <a class="iref" href="#rfc.xref.Part3.5">3.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a></li>3231 <li class="indline1"><em> Appendix</em> <a class="iref" href="#rfc.xref.Part3.7">3.5</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a></li>3232 <li class="indline1"><em>Appendix </em> <a class="iref" href="#rfc.xref.Part3.13">C</a></li>3226 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part3.5">3.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a></li> 3227 <li class="indline1"><em>Section 2.3</em> <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li> 3228 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li> 3229 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part3.13">C</a></li> 3230 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li> 3231 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.7">3.5</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a></li> 3232 <li class="indline1"><em>Appendix A</em> <a class="iref" href="#rfc.xref.Part3.1">1</a></li> 3233 3233 </ul> 3234 3234 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r457 r458 369 369 </t> 370 370 <figure><artwork type="example"> 371 #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ]372 373 1#element => *( "," OWS ) element *( OWS "," [ OWS element ] )371 #element => [ ( "," / element ) *( OWS "," [ OWS element ] ) ] 372 373 1#element => *( "," OWS ) element *( OWS "," [ OWS element ] ) 374 374 </artwork></figure> 375 375 <t> … … 853 853 </t> 854 854 <figure><artwork type="example"> 855 856 857 855 Sun, 06 Nov 1994 08:49:37 GMT ; RFC 1123 856 Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 857 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 858 858 </artwork></figure> 859 859 <t> … … 1130 1130 </t> 1131 1131 <figure><artwork type="example"> 1132 1133 1132 User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1133 Server: Apache/0.8.4 1134 1134 </artwork></figure> 1135 1135 <t> -
draft-ietf-httpbis/latest/p3-payload.html
r457 r458 815 815 by the IANA. Example tags include: 816 816 </p> 817 <div id="rfc.figure.u.11"></div><pre class="text"> 817 <div id="rfc.figure.u.11"></div><pre class="text"> en, en-US, en-cockney, i-cherokee, x-pig-latin 818 818 </pre><p id="rfc.section.2.4.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country 819 819 code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered … … 856 856 and Content-Encoding. These define a two-layer, ordered encoding model: 857 857 </p> 858 <div id="rfc.figure.u.14"></div><pre class="text"> 858 <div id="rfc.figure.u.14"></div><pre class="text"> entity-body := Content-Encoding( Content-Type( data ) ) 859 859 </pre><p id="rfc.section.3.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content 860 860 codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There … … 1657 1657 <a href="#content-disposition" class="smpl">disp-extension-parm</a> = <a href="#core.rules" class="smpl">token</a> "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) 1658 1658 </pre><p id="rfc.section.B.1.p.3">An example is</p> 1659 <div id="rfc.figure.u.39"></div><pre class="text"> 1659 <div id="rfc.figure.u.39"></div><pre class="text"> Content-Disposition: attachment; filename="fname.ext" 1660 1660 </pre><p id="rfc.section.B.1.p.5">The receiving user agent <em class="bcp14">SHOULD NOT</em> respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply 1661 1661 to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only. -
draft-ietf-httpbis/latest/p3-payload.xml
r457 r458 634 634 </t> 635 635 <figure><artwork type="example"> 636 636 en, en-US, en-cockney, i-cherokee, x-pig-latin 637 637 </artwork></figure> 638 638 <t> … … 710 710 </t> 711 711 <figure><artwork type="example"> 712 712 entity-body := Content-Encoding( Content-Type( data ) ) 713 713 </artwork></figure> 714 714 <t> … … 2569 2569 </t> 2570 2570 <figure><artwork type="example"> 2571 2571 Content-Disposition: attachment; filename="fname.ext" 2572 2572 </artwork></figure> 2573 2573 <t> -
draft-ietf-httpbis/latest/p6-cache.html
r454 r458 982 982 than the one for the existing entry, then the client <em class="bcp14">SHOULD</em> repeat the request unconditionally, and include 983 983 </p> 984 <div id="rfc.figure.u.9"></div><pre class="text"> 984 <div id="rfc.figure.u.9"></div><pre class="text"> Cache-Control: max-age=0 985 985 </pre><p id="rfc.section.3.6.p.5">to force any intermediate caches to validate their copies directly with the origin server, or</p> 986 <div id="rfc.figure.u.10"></div><pre class="text"> 986 <div id="rfc.figure.u.10"></div><pre class="text"> Cache-Control: no-cache 987 987 </pre><p id="rfc.section.3.6.p.7">to force any intermediate caches to obtain a new copy from the origin server.</p> 988 988 <p id="rfc.section.3.6.p.8">If the Date values are equal, then the client <em class="bcp14">MAY</em> use either response (or <em class="bcp14">MAY</em>, if it is being extremely prudent, request a new response). Servers <em class="bcp14">MUST NOT</em> depend on clients being able to choose deterministically between responses generated during the same second, if their expiration … … 1559 1559 an otherwise private response in their shared cache(s) could do so by including 1560 1560 </p> 1561 <div id="rfc.figure.u.14"></div><pre class="text"> 1561 <div id="rfc.figure.u.14"></div><pre class="text"> Cache-Control: private, community="UCI" 1562 1562 </pre><p id="rfc.section.15.2.6.p.5">A cache seeing this header field will act correctly even if the cache does not understand the community cache-extension, since 1563 1563 it will also see and understand the private directive and thus default to the safe behavior. -
draft-ietf-httpbis/latest/p6-cache.xml
r454 r458 994 994 </t> 995 995 <figure><artwork type="example"> 996 996 Cache-Control: max-age=0 997 997 </artwork></figure> 998 998 <t> … … 1001 1001 </t> 1002 1002 <figure><artwork type="example"> 1003 1003 Cache-Control: no-cache 1004 1004 </artwork></figure> 1005 1005 <t> … … 2087 2087 </t> 2088 2088 <figure><artwork type="example"> 2089 2089 Cache-Control: private, community="UCI" 2090 2090 </artwork></figure> 2091 2091 <t>
Note: See TracChangeset
for help on using the changeset viewer.