Changeset 531
- Timestamp:
- 05/03/09 10:13:53 (13 years ago)
- Location:
- draft-ietf-httpbis/latest-roy
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest-roy/p1-messaging.html
r500 r531 375 375 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 376 376 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 377 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 4, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">377 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.425, 2009-03-02 15:29:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 378 378 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 379 379 <meta name="DC.Creator" content="Fielding, R."> … … 471 471 <tr> 472 472 <td class="header left"></td> 473 <td class="header right">March 4, 2009</td>473 <td class="header right">March 5, 2009</td> 474 474 </tr> 475 475 </table> … … 2649 2649 <div id="rfc.figure.u.65"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS 2650 2650 2651 <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, defined in [Part6], Section 15.4>2651 <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, defined in [Part6], Section 3.4> 2652 2652 <a href="#chunked.transfer.encoding" class="smpl">Chunked-Body</a> = *chunk last-chunk trailer-part CRLF 2653 2653 <a href="#header.connection" class="smpl">Connection</a> = "Connection:" OWS Connection-v … … 2673 2673 <a href="#rule.whitespace" class="smpl">OWS</a> = *( [ obs-fold ] WSP ) 2674 2674 2675 <a href="#abnf.dependencies" class="smpl">Pragma</a> = <Pragma, defined in [Part6], Section 15.4>2675 <a href="#abnf.dependencies" class="smpl">Pragma</a> = <Pragma, defined in [Part6], Section 3.4> 2676 2676 2677 2677 <a href="#rule.whitespace" class="smpl">RWS</a> = 1*( [ obs-fold ] WSP ) … … 2704 2704 ] ) 2705 2705 2706 <a href="#abnf.dependencies" class="smpl">Warning</a> = <Warning, defined in [Part6], Section 15.6>2706 <a href="#abnf.dependencies" class="smpl">Warning</a> = <Warning, defined in [Part6], Section 3.6> 2707 2707 2708 2708 <a href="#uri" class="smpl">absolute-URI</a> = <absolute-URI, defined in [RFC3986], Section 4.3> -
draft-ietf-httpbis/latest-roy/p1-messaging.xml
r500 r531 4436 4436 <x:ref>BWS</x:ref> = OWS 4437 4437 4438 <x:ref>Cache-Control</x:ref> = <Cache-Control, defined in [Part6], Section 15.4>4438 <x:ref>Cache-Control</x:ref> = <Cache-Control, defined in [Part6], Section 3.4> 4439 4439 <x:ref>Chunked-Body</x:ref> = *chunk last-chunk trailer-part CRLF 4440 4440 <x:ref>Connection</x:ref> = "Connection:" OWS Connection-v … … 4460 4460 <x:ref>OWS</x:ref> = *( [ obs-fold ] WSP ) 4461 4461 4462 <x:ref>Pragma</x:ref> = <Pragma, defined in [Part6], Section 15.4>4462 <x:ref>Pragma</x:ref> = <Pragma, defined in [Part6], Section 3.4> 4463 4463 4464 4464 <x:ref>RWS</x:ref> = 1*( [ obs-fold ] WSP ) … … 4491 4491 ] ) 4492 4492 4493 <x:ref>Warning</x:ref> = <Warning, defined in [Part6], Section 15.6>4493 <x:ref>Warning</x:ref> = <Warning, defined in [Part6], Section 3.6> 4494 4494 4495 4495 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [RFC3986], Section 4.3> -
draft-ietf-httpbis/latest-roy/p2-semantics.html
r500 r531 371 371 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 372 372 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 373 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 4, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">373 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.425, 2009-03-02 15:29:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 374 374 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 375 375 <meta name="DC.Creator" content="Fielding, R."> … … 468 468 <tr> 469 469 <td class="header left"></td> 470 <td class="header right">March 4, 2009</td>470 <td class="header right">March 5, 2009</td> 471 471 </tr> 472 472 </table> … … 2251 2251 <a href="#abnf.dependencies" class="smpl">Accept-Language</a> = <Accept-Language, defined in [Part3], Section 5.4> 2252 2252 <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a> = <Accept-Ranges, defined in [Part5], Section 5.1> 2253 <a href="#abnf.dependencies" class="smpl">Age</a> = <Age, defined in [Part6], Section 15.1>2253 <a href="#abnf.dependencies" class="smpl">Age</a> = <Age, defined in [Part6], Section 3.1> 2254 2254 <a href="#header.allow" class="smpl">Allow</a> = "Allow:" OWS Allow-v 2255 2255 <a href="#header.allow" class="smpl">Allow-v</a> = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ] … … 2312 2312 <a href="#header.user-agent" class="smpl">User-Agent-v</a> = product *( RWS ( product / comment ) ) 2313 2313 2314 <a href="#abnf.dependencies" class="smpl">Vary</a> = <Vary, defined in [Part6], Section 15.5>2314 <a href="#abnf.dependencies" class="smpl">Vary</a> = <Vary, defined in [Part6], Section 3.5> 2315 2315 2316 2316 WWW-Authenticate = -
draft-ietf-httpbis/latest-roy/p2-semantics.xml
r500 r531 3213 3213 <x:ref>Accept-Language</x:ref> = <Accept-Language, defined in [Part3], Section 5.4> 3214 3214 <x:ref>Accept-Ranges</x:ref> = <Accept-Ranges, defined in [Part5], Section 5.1> 3215 <x:ref>Age</x:ref> = <Age, defined in [Part6], Section 15.1>3215 <x:ref>Age</x:ref> = <Age, defined in [Part6], Section 3.1> 3216 3216 <x:ref>Allow</x:ref> = "Allow:" OWS Allow-v 3217 3217 <x:ref>Allow-v</x:ref> = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ] … … 3274 3274 <x:ref>User-Agent-v</x:ref> = product *( RWS ( product / comment ) ) 3275 3275 3276 <x:ref>Vary</x:ref> = <Vary, defined in [Part6], Section 15.5>3276 <x:ref>Vary</x:ref> = <Vary, defined in [Part6], Section 3.5> 3277 3277 3278 3278 WWW-Authenticate = -
draft-ietf-httpbis/latest-roy/p3-payload.html
r500 r531 379 379 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 380 380 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 381 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 4, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">381 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.425, 2009-03-02 15:29:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 382 382 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 383 383 <meta name="DC.Creator" content="Fielding, R."> … … 475 475 <tr> 476 476 <td class="header left"></td> 477 <td class="header right">March 4, 2009</td>477 <td class="header right">March 5, 2009</td> 478 478 </tr> 479 479 </table> … … 1749 1749 <a href="#header.content-type" class="smpl">Content-Type-v</a> = media-type 1750 1750 1751 <a href="#abnf.dependencies" class="smpl">Expires</a> = <Expires, defined in [Part6], Section 15.3>1751 <a href="#abnf.dependencies" class="smpl">Expires</a> = <Expires, defined in [Part6], Section 3.3> 1752 1752 1753 1753 <a href="#abnf.dependencies" class="smpl">Last-Modified</a> = <Last-Modified, defined in [Part4], Section 6.6> -
draft-ietf-httpbis/latest-roy/p3-payload.xml
r500 r531 2667 2667 <x:ref>Content-Type-v</x:ref> = media-type 2668 2668 2669 <x:ref>Expires</x:ref> = <Expires, defined in [Part6], Section 15.3>2669 <x:ref>Expires</x:ref> = <Expires, defined in [Part6], Section 3.3> 2670 2670 2671 2671 <x:ref>Last-Modified</x:ref> = <Last-Modified, defined in [Part4], Section 6.6> -
draft-ietf-httpbis/latest-roy/p4-conditional.html
r500 r531 368 368 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 369 369 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 4, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.425, 2009-03-02 15:29:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 371 371 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 372 372 <meta name="DC.Creator" content="Fielding, R."> … … 464 464 <tr> 465 465 <td class="header left"></td> 466 <td class="header right">March 4, 2009</td>466 <td class="header right">March 5, 2009</td> 467 467 </tr> 468 468 </table> -
draft-ietf-httpbis/latest-roy/p5-range.html
r500 r531 368 368 <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C"> 369 369 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 4, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.425, 2009-03-02 15:29:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 371 371 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 372 372 <meta name="DC.Creator" content="Fielding, R."> … … 464 464 <tr> 465 465 <td class="header left"></td> 466 <td class="header right">March 4, 2009</td>466 <td class="header right">March 5, 2009</td> 467 467 </tr> 468 468 </table> -
draft-ietf-httpbis/latest-roy/p6-cache.html
r529 r531 687 687 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="caching.overview" href="#caching.overview">Cache Operation</a></h1> 688 688 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="response.cacheability" href="#response.cacheability">Response Cacheability</a></h2> 689 <p id="rfc.section.2.1.p.1">A cache <em class="bcp14">M AY</em> store a response to any request, provided that:689 <p id="rfc.section.2.1.p.1">A cache <em class="bcp14">MUST NOT</em> store a response to any request, unless: 690 690 </p> 691 691 <ul> … … 704 704 </p> 705 705 <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a> <a id="errors.or.incomplete.response.cache.behavior" href="#errors.or.incomplete.response.cache.behavior">Storing Partial and Incomplete Responses</a></h3> 706 <p id="rfc.section.2.1.1.p.1">A cache that receives an incomplete response (for example, with fewer bytes of data than specified in a Content-Length header) <em class="bcp14">MAY</em> store the response. However, the cache <em class="bcp14">MUST</em> treat this as a partial response <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. Partial responses <em class="bcp14">MAY</em> be combined as described in <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 4</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>; the result might be a full response or might still be partial. A cache <em class="bcp14">MUST NOT</em> return a partial response to a client without explicitly marking it as such using the 206 (Partial Content) status code. 706 <p id="rfc.section.2.1.1.p.1">A cache that receives an incomplete response (for example, with fewer bytes of data than specified in a Content-Length header) 707 can store the response, but <em class="bcp14">MUST</em> treat it as a partial response <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. Partial responses can be combined as described in <a href="p5-range.html#combining.byte.ranges" title="Combining Ranges">Section 4</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>; the result might be a full response or might still be partial. A cache <em class="bcp14">MUST NOT</em> return a partial response to a client without explicitly marking it as such using the 206 (Partial Content) status code. 707 708 </p> 708 709 <p id="rfc.section.2.1.1.p.2">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> store incomplete or partial responses. 709 710 </p> 710 711 <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="constructing.responses.from.caches" href="#constructing.responses.from.caches">Constructing Responses from Caches</a></h2> 711 <p id="rfc.section.2.2.p.1">For a presented request, a cache <em class="bcp14">M AY</em> return a stored response, provided that:712 <p id="rfc.section.2.2.p.1">For a presented request, a cache <em class="bcp14">MUST NOT</em> return a stored response, unless: 712 713 </p> 713 714 <ul> … … 737 738 <p id="rfc.section.2.2.p.5">Also, note that unsafe requests might invalidate already stored responses; see <a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a>. 738 739 </p> 739 <p id="rfc.section.2.2.p.6">Caches <em class="bcp14">MUST</em> use the most recent response (as determined by the Date header) when more than one suitable response is stored. They <em class="bcp14">MAY</em> also forward a request with "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use. 740 <p id="rfc.section.2.2.p.6">Caches <em class="bcp14">MUST</em> use the most recent response (as determined by the Date header) when more than one suitable response is stored. They can also 741 forward a request with "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use. 740 742 </p> 741 743 <p id="rfc.section.2.2.p.7"> <span class="comment">[rfc.comment.4: TODO: end-to-end and hop-by-hop headers, non-modifiable headers removed; re-spec in p1]</span> … … 749 751 likely to change in a semantically significant way before the expiration time is reached. 750 752 </p> 751 <p id="rfc.section.2.3.p.3">If an origin server wishes to force a cache to validate every request, it <em class="bcp14">MAY</em> assign an explicit expiration time in the past. This means that the response is always stale, so that caches should validate752 it before using it for subsequent requests. <span class="comment">[rfc.comment.5: This wording may cause confusion, because the response may still be served stale.]</span></p>753 <p id="rfc.section.2.3.p.3">If an origin server wishes to force a cache to validate every request, it can assign an explicit expiration time in the past. 754 This means that the response is always stale, so that caches should validate it before using it for subsequent requests. <span class="comment">[rfc.comment.5: This wording may cause confusion, because the response may still be served stale.]</span></p> 753 755 <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, HTTP caches may also assign heuristic expiration times 754 756 when they are not specified, employing algorithms that use other header values (such as the Last-Modified time) to estimate … … 783 785 <h4 id="rfc.section.2.3.1.1"><a href="#rfc.section.2.3.1.1">2.3.1.1</a> <a id="heuristic.freshness" href="#heuristic.freshness">Calculating Heuristic Freshness</a></h4> 784 786 <p id="rfc.section.2.3.1.1.p.1">If no explicit expiration time is present in a stored response that has a status code of 200, 203, 206, 300, 301 or 410, a 785 heuristic expiration time <em class="bcp14">MAY</em>be calculated. Heuristics <em class="bcp14">MUST NOT</em> be used for other response status codes.787 heuristic expiration time can be calculated. Heuristics <em class="bcp14">MUST NOT</em> be used for other response status codes. 786 788 </p> 787 789 <p id="rfc.section.2.3.1.1.p.2">When a heuristic is used to calculate freshness lifetime, the cache <em class="bcp14">SHOULD</em> attach a Warning header with a 113 warn-code to the response if its current_age is more than 24 hours and such a warning is … … 840 842 but is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section 2.3</a>. 841 843 </p> 842 <p id="rfc.section.2.3.3.p.2">Caches <em class="bcp14">MAY</em> return a stale response if disconnected (i.e., it cannot contact the origin server or otherwise find a forward path) or explicitly 843 allowed (e.g., the max-stale request directive; see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a>). 844 </p> 845 <p id="rfc.section.2.3.3.p.3">Caches <em class="bcp14">MUST NOT</em> return a stale response if it is prohibited by an explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache 844 <p id="rfc.section.2.3.3.p.2">Caches <em class="bcp14">MUST NOT</em> return a stale response if it is prohibited by an explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache 846 845 directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive; 847 846 see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>). 848 847 </p> 849 <p id="rfc.section.2.3.3.p.4">Otherwise, caches <em class="bcp14">SHOULD NOT</em> return stale responses. 850 </p> 851 <p id="rfc.section.2.3.3.p.5">Stale responses <em class="bcp14">SHOULD</em> have a Warning header with the 110 warn-code (see <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">Section 3.6</a>). Likewise, the 112 warn-code <em class="bcp14">SHOULD</em> be sent on stale responses if the cache is disconnected. 852 </p> 853 <p id="rfc.section.2.3.3.p.6">If a cache receives a first-hand response (either an entire response, or a 304 (Not Modified) response) that it would normally 848 <p id="rfc.section.2.3.3.p.3">Caches <em class="bcp14">SHOULD NOT</em> return stale responses unless they are disconnected (i.e., it cannot contact the origin server or otherwise find a forward 849 path) or otherwise explicitly allowed (e.g., the max-stale request directive; see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a>).. 850 </p> 851 <p id="rfc.section.2.3.3.p.4">Stale responses <em class="bcp14">SHOULD</em> have a Warning header with the 110 warn-code (see <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">Section 3.6</a>). Likewise, the 112 warn-code <em class="bcp14">SHOULD</em> be sent on stale responses if the cache is disconnected. 852 </p> 853 <p id="rfc.section.2.3.3.p.5">If a cache receives a first-hand response (either an entire response, or a 304 (Not Modified) response) that it would normally 854 854 forward to the requesting client, and the received response is no longer fresh, the cache <em class="bcp14">SHOULD</em> forward it to the requesting client without adding a new Warning (but without removing any existing Warning headers). A cache <em class="bcp14">SHOULD NOT</em> attempt to validate a response simply because that response became stale in transit. 855 855 </p> … … 1139 1139 <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a> <a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3> 1140 1140 <p id="rfc.section.3.2.3.p.1">The Cache-Control header field can be extended through the use of one or more cache-extension tokens, each with an optional 1141 value. Informational extensions (those that do not require a change in cache behavior) <em class="bcp14">MAY</em> be added without changing the semantics of other directives. Behavioral extensions are designed to work by acting as modifiers 1142 to the existing base of cache directives. Both the new directive and the standard directive are supplied, such that applications 1143 that do not understand the new directive will default to the behavior specified by the standard directive, and those that 1144 understand the new directive will recognize it as modifying the requirements associated with the standard directive. In this 1145 way, extensions to the cache-control directives can be made without requiring changes to the base protocol. 1141 value. Informational extensions (those that do not require a change in cache behavior) can be added without changing the semantics 1142 of other directives. Behavioral extensions are designed to work by acting as modifiers to the existing base of cache directives. 1143 Both the new directive and the standard directive are supplied, such that applications that do not understand the new directive 1144 will default to the behavior specified by the standard directive, and those that understand the new directive will recognize 1145 it as modifying the requirements associated with the standard directive. In this way, extensions to the cache-control directives 1146 can be made without requiring changes to the base protocol. 1146 1147 </p> 1147 1148 <p id="rfc.section.3.2.3.p.2">This extension mechanism depends on an HTTP cache obeying all of the cache-control directives defined for its native HTTP-version, … … 1254 1255 <a href="#header.warning" class="smpl">warn-text</a> = <a href="#core.rules" class="smpl">quoted-string</a> 1255 1256 <a href="#header.warning" class="smpl">warn-date</a> = <a href="#notation" class="smpl">DQUOTE</a> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> <a href="#notation" class="smpl">DQUOTE</a> 1256 </pre><p id="rfc.section.3.6.p.5">Multiple warnings <em class="bcp14">MAY</em> be attached to a response (either by the origin server or by a cache), including multiple warnings with the same code number.1257 For example, a server might provide the same warning with texts in both English and Basque.1257 </pre><p id="rfc.section.3.6.p.5">Multiple warnings can be attached to a response (either by the origin server or by a cache), including multiple warnings with 1258 the same code number. For example, a server might provide the same warning with texts in both English and Basque. 1258 1259 </p> 1259 1260 <p id="rfc.section.3.6.p.6">When this occurs, the user agent <em class="bcp14">SHOULD</em> inform the user of as many of them as possible, in the order that they appear in the response. If it is not possible to inform … … 1319 1320 <p id="rfc.section.3.6.p.18">199 Miscellaneous warning </p> 1320 1321 <dl class="empty"> 1321 <dd>The warning text <em class="bcp14">MAY</em>include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action, besides presenting the warning to the user.1322 <dd>The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action, besides presenting the warning to the user. 1322 1323 </dd> 1323 1324 </dl> … … 1331 1332 <p id="rfc.section.3.6.p.20">299 Miscellaneous persistent warning </p> 1332 1333 <dl class="empty"> 1333 <dd>The warning text <em class="bcp14">MAY</em>include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action.1334 <dd>The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action. 1334 1335 </dd> 1335 1336 </dl> -
draft-ietf-httpbis/latest-roy/p7-auth.html
r501 r531 365 365 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 366 366 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 367 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 4, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">367 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.425, 2009-03-02 15:29:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 368 368 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 369 369 <meta name="DC.Creator" content="Fielding, R."> … … 462 462 <tr> 463 463 <td class="header left"></td> 464 <td class="header right">March 4, 2009</td>464 <td class="header right">March 5, 2009</td> 465 465 </tr> 466 466 </table>
Note: See TracChangeset
for help on using the changeset viewer.