Changeset 1578 for draft-ietf-httpbis
- Timestamp:
- 10/03/12 12:38:56 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r1573 r1578 460 460 } 461 461 @bottom-center { 462 content: "Expires September 1 0, 2012";462 content: "Expires September 11, 2012"; 463 463 } 464 464 @bottom-right { … … 511 511 <meta name="dct.creator" content="Reschke, J. F."> 512 512 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 513 <meta name="dct.issued" scheme="ISO8601" content="2012-03- 09">513 <meta name="dct.issued" scheme="ISO8601" content="2012-03-10"> 514 514 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 515 515 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 537 537 </tr> 538 538 <tr> 539 <td class="left">Expires: September 1 0, 2012</td>539 <td class="left">Expires: September 11, 2012</td> 540 540 <td class="right">J. Mogul</td> 541 541 </tr> … … 594 594 <tr> 595 595 <td class="left"></td> 596 <td class="right">March 9, 2012</td>596 <td class="right">March 10, 2012</td> 597 597 </tr> 598 598 </tbody> … … 622 622 in progress”. 623 623 </p> 624 <p>This Internet-Draft will expire on September 1 0, 2012.</p>624 <p>This Internet-Draft will expire on September 11, 2012.</p> 625 625 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 626 626 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 806 806 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>> 807 807 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>> 808 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 5.4.1</a>>808 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.4.1</a>> 809 809 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> 810 810 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="character.sets" href="#character.sets">Character Encodings (charset)</a></h2> … … 838 838 </p> 839 839 <ul class="empty"> 840 <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 5.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.840 <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 841 841 </li> 842 842 </ul> … … 844 844 </p> 845 845 <ul class="empty"> 846 <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 5.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.846 <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 847 847 </li> 848 848 </ul> … … 850 850 </p> 851 851 <ul class="empty"> 852 <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 5.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.852 <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 853 853 </li> 854 854 </ul> … … 862 862 <li>Pointer to specification text</li> 863 863 </ul> 864 <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 5</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 5.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).864 <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 865 865 </p> 866 866 <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section. … … 1128 1128 that doesn't conform to them is better than sending a 406 (Not Acceptable) response. 1129 1129 </p> 1130 <p id="rfc.section.5.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 5.4.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information.1130 <p id="rfc.section.5.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.4.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information. 1131 1131 </p> 1132 1132 <p id="rfc.section.5.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities … … 1181 1181 <p id="rfc.section.6.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first 1182 1182 "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user 1183 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 5.4.1</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.1183 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.4.1</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1. 1184 1184 </p> 1185 1185 <div class="note" id="rfc.section.6.1.p.5"> … … 1311 1311 </li> 1312 1312 <li>If the representation's content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable 1313 unless it is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 5.4.1</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)1313 unless it is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.4.1</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".) 1314 1314 </li> 1315 1315 <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li> … … 1425 1425 </p> 1426 1426 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.22"></span> <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a> 1427 </pre><p id="rfc.section.6.7.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME1427 </pre><p id="rfc.section.6.7.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.6</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME 1428 1428 body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients. 1429 1429 </p> … … 1573 1573 <td class="left">compress</td> 1574 1574 <td class="left">UNIX "compress" program method</td> 1575 <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 5.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>1575 <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1576 1576 </td> 1577 1577 </tr> … … 1580 1580 <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>) 1581 1581 </td> 1582 <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 5.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>1582 <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1583 1583 </td> 1584 1584 </tr> … … 1586 1586 <td class="left">gzip</td> 1587 1587 <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 1588 <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 5.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>1588 <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1589 1589 </td> 1590 1590 </tr> … … 1935 1935 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in [Part1], Section 2.7> 1936 1936 1937 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in [Part1], Section 5.4.1>1937 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in [Part1], Section 4.4.1> 1938 1938 1939 1939 <a href="#media.types" class="smpl">subtype</a> = token … … 2284 2284 <li><em>Section 3.3.1</em> <a href="#rfc.xref.Part1.25">A.6</a></li> 2285 2285 <li><em>Section 3.3.2</em> <a href="#rfc.xref.Part1.15">3.1</a></li> 2286 <li><em>Section 4 .3</em> <a href="#rfc.xref.Part1.20">6.7</a></li>2287 <li><em>Section 5</em> <a href="#rfc.xref.Part1.13">2.2.1</a></li>2288 <li><em>Section 5.2.1</em> <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.21">7.2</a></li>2289 <li><em>Section 5.2</em> <a href="#rfc.xref.Part1.14">2.2.1</a></li>2290 <li><em>Section 5.2.2</em> <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.22">7.2</a></li>2291 <li><em>Section 5.2.3</em> <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.23">7.2</a></li>2292 <li><em>Section 5. 4.1</em> <a href="#rfc.xref.Part1.9">1.3.2</a>, <a href="#rfc.xref.Part1.17">5.1</a>, <a href="#rfc.xref.Part1.18">6.1</a>, <a href="#rfc.xref.Part1.19">6.3</a></li>2286 <li><em>Section 4</em> <a href="#rfc.xref.Part1.13">2.2.1</a></li> 2287 <li><em>Section 4.2.1</em> <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.21">7.2</a></li> 2288 <li><em>Section 4.2</em> <a href="#rfc.xref.Part1.14">2.2.1</a></li> 2289 <li><em>Section 4.2.2</em> <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.22">7.2</a></li> 2290 <li><em>Section 4.2.3</em> <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.23">7.2</a></li> 2291 <li><em>Section 4.4.1</em> <a href="#rfc.xref.Part1.9">1.3.2</a>, <a href="#rfc.xref.Part1.17">5.1</a>, <a href="#rfc.xref.Part1.18">6.1</a>, <a href="#rfc.xref.Part1.19">6.3</a></li> 2292 <li><em>Section 5.6</em> <a href="#rfc.xref.Part1.20">6.7</a></li> 2293 2293 <li><em>Section 11</em> <a href="#rfc.xref.Part1.24">9</a></li> 2294 2294 </ul> -
draft-ietf-httpbis/latest/p3-payload.xml
r1573 r1578 2635 2635 <x:ref>partial-URI</x:ref> = <partial-URI, defined in [Part1], Section 2.7> 2636 2636 2637 <x:ref>qvalue</x:ref> = <qvalue, defined in [Part1], Section 5.4.1>2637 <x:ref>qvalue</x:ref> = <qvalue, defined in [Part1], Section 4.4.1> 2638 2638 2639 2639 <x:ref>subtype</x:ref> = token -
draft-ietf-httpbis/latest/p6-cache.html
r1567 r1578 463 463 } 464 464 @bottom-center { 465 content: "Expires September 9, 2012";465 content: "Expires September 11, 2012"; 466 466 } 467 467 @bottom-right { … … 511 511 <meta name="dct.creator" content="Reschke, J. F."> 512 512 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 513 <meta name="dct.issued" scheme="ISO8601" content="2012-03- 08">513 <meta name="dct.issued" scheme="ISO8601" content="2012-03-10"> 514 514 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 515 515 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 537 537 </tr> 538 538 <tr> 539 <td class="left">Expires: September 9, 2012</td>539 <td class="left">Expires: September 11, 2012</td> 540 540 <td class="right">J. Mogul</td> 541 541 </tr> … … 602 602 <tr> 603 603 <td class="left"></td> 604 <td class="right">March 8, 2012</td>604 <td class="right">March 10, 2012</td> 605 605 </tr> 606 606 </tbody> … … 632 632 in progress”. 633 633 </p> 634 <p>This Internet-Draft will expire on September 9, 2012.</p>634 <p>This Internet-Draft will expire on September 11, 2012.</p> 635 635 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 636 636 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 880 880 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, 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#http.date" title="Date/Time Formats">Section 8</a>> 881 881 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>> 882 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 8. 4</a>>882 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 8.3</a>> 883 883 <a href="#abnf.dependencies" class="smpl">uri-host</a> = <uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>> 884 884 </pre><h2 id="rfc.section.1.5"><a href="#rfc.section.1.5">1.5</a> <a id="delta-seconds" href="#delta-seconds">Delta Seconds</a></h2> … … 953 953 </p> 954 954 <ul> 955 <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and that of the stored response match, and955 <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.6</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and that of the stored response match, and 956 956 </li> 957 957 <li>the request method associated with the stored response allows it to be used for the presented request, and</li> … … 1210 1210 to keep their contents up-to-date. 1211 1211 </p> 1212 <p id="rfc.section.2.6.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location response header fields (if present) when a non-error response1212 <p id="rfc.section.2.6.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.6</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) as well as the URI(s) in the Location and Content-Location response header fields (if present) when a non-error response 1213 1213 to a request with an unsafe method is received. 1214 1214 </p> 1215 1215 <p id="rfc.section.2.6.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a Location or Content-Location response header field if the host part of that URI differs from the host 1216 part in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). This helps prevent denial of service attacks.1217 </p> 1218 <p id="rfc.section.2.6.p.4">A cache <em class="bcp14">MUST</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.1216 part in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.6</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). This helps prevent denial of service attacks. 1217 </p> 1218 <p id="rfc.section.2.6.p.4">A cache <em class="bcp14">MUST</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.6</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown. 1219 1219 </p> 1220 1220 <p id="rfc.section.2.6.p.5">Here, a "non-error response" is one with a 2xx or 3xx status code. "Invalidate" means that the cache will either remove all … … 2076 2076 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in [Part1], Section 2.7> 2077 2077 <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma 2078 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in [Part1], Section 8. 4>2078 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in [Part1], Section 8.3> 2079 2079 2080 2080 <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 3.2.4> … … 2475 2475 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.16">2.8</a></li> 2476 2476 <li><em>Section 3.2.4</em> <a href="#rfc.xref.Part1.5">1.4.1</a>, <a href="#rfc.xref.Part1.6">1.4.1</a></li> 2477 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.6</a>, <a href="#rfc.xref.Part1.14">2.6</a>, <a href="#rfc.xref.Part1.15">2.6</a></li>2478 <li><em>Section 8. 4</em> <a href="#rfc.xref.Part1.9">1.4.2</a></li>2477 <li><em>Section 5.6</em> <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.6</a>, <a href="#rfc.xref.Part1.14">2.6</a>, <a href="#rfc.xref.Part1.15">2.6</a></li> 2478 <li><em>Section 8.3</em> <a href="#rfc.xref.Part1.9">1.4.2</a></li> 2479 2479 <li><em>Section 11</em> <a href="#rfc.xref.Part1.17">7</a></li> 2480 2480 </ul> -
draft-ietf-httpbis/latest/p6-cache.xml
r1567 r1578 2666 2666 <x:ref>port</x:ref> = <port, defined in [Part1], Section 2.7> 2667 2667 <x:ref>pragma-directive</x:ref> = "no-cache" / extension-pragma 2668 <x:ref>pseudonym</x:ref> = <pseudonym, defined in [Part1], Section 8. 4>2668 <x:ref>pseudonym</x:ref> = <pseudonym, defined in [Part1], Section 8.3> 2669 2669 2670 2670 <x:ref>quoted-string</x:ref> = <quoted-string, defined in [Part1], Section 3.2.4>
Note: See TracChangeset
for help on using the changeset viewer.