Changeset 531


Ignore:
Timestamp:
Mar 5, 2009, 2:13:53 AM (11 years ago)
Author:
julian.reschke@…
Message:

regenerate HTML

Location:
draft-ietf-httpbis/latest-roy
Files:
10 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest-roy/p1-messaging.html

    r500 r531  
    375375      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
    376376      <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.424, 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/">
    378378      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    379379      <meta name="DC.Creator" content="Fielding, R.">
    … …  
    471471         <tr>
    472472            <td class="header left"></td>
    473             <td class="header right">March 4, 2009</td>
     473            <td class="header right">March 5, 2009</td>
    474474         </tr>
    475475      </table>
    … …  
    26492649      <div id="rfc.figure.u.65"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS
    26502650
    2651 <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = &lt;Cache-Control, defined in [Part6], Section 15.4&gt;
     2651<a href="#abnf.dependencies" class="smpl">Cache-Control</a> = &lt;Cache-Control, defined in [Part6], Section 3.4&gt;
    26522652<a href="#chunked.transfer.encoding" class="smpl">Chunked-Body</a> = *chunk last-chunk trailer-part CRLF
    26532653<a href="#header.connection" class="smpl">Connection</a> = "Connection:" OWS Connection-v
    … …  
    26732673<a href="#rule.whitespace" class="smpl">OWS</a> = *( [ obs-fold ] WSP )
    26742674
    2675 <a href="#abnf.dependencies" class="smpl">Pragma</a> = &lt;Pragma, defined in [Part6], Section 15.4&gt;
     2675<a href="#abnf.dependencies" class="smpl">Pragma</a> = &lt;Pragma, defined in [Part6], Section 3.4&gt;
    26762676
    26772677<a href="#rule.whitespace" class="smpl">RWS</a> = 1*( [ obs-fold ] WSP )
    … …  
    27042704 ] )
    27052705
    2706 <a href="#abnf.dependencies" class="smpl">Warning</a> = &lt;Warning, defined in [Part6], Section 15.6&gt;
     2706<a href="#abnf.dependencies" class="smpl">Warning</a> = &lt;Warning, defined in [Part6], Section 3.6&gt;
    27072707
    27082708<a href="#uri" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;

  • draft-ietf-httpbis/latest-roy/p1-messaging.xml

    r500 r531  
    44364436<x:ref>BWS</x:ref> = OWS
    44374437
    4438 <x:ref>Cache-Control</x:ref> = &lt;Cache-Control, defined in [Part6], Section 15.4&gt;
     4438<x:ref>Cache-Control</x:ref> = &lt;Cache-Control, defined in [Part6], Section 3.4&gt;
    44394439<x:ref>Chunked-Body</x:ref> = *chunk last-chunk trailer-part CRLF
    44404440<x:ref>Connection</x:ref> = "Connection:" OWS Connection-v
    … …  
    44604460<x:ref>OWS</x:ref> = *( [ obs-fold ] WSP )
    44614461
    4462 <x:ref>Pragma</x:ref> = &lt;Pragma, defined in [Part6], Section 15.4&gt;
     4462<x:ref>Pragma</x:ref> = &lt;Pragma, defined in [Part6], Section 3.4&gt;
    44634463
    44644464<x:ref>RWS</x:ref> = 1*( [ obs-fold ] WSP )
    … …  
    44914491 ] )
    44924492
    4493 <x:ref>Warning</x:ref> = &lt;Warning, defined in [Part6], Section 15.6&gt;
     4493<x:ref>Warning</x:ref> = &lt;Warning, defined in [Part6], Section 3.6&gt;
    44944494
    44954495<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;

  • draft-ietf-httpbis/latest-roy/p2-semantics.html

    r500 r531  
    371371      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    372372      <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.424, 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/">
    374374      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    375375      <meta name="DC.Creator" content="Fielding, R.">
    … …  
    468468         <tr>
    469469            <td class="header left"></td>
    470             <td class="header right">March 4, 2009</td>
     470            <td class="header right">March 5, 2009</td>
    471471         </tr>
    472472      </table>
    … …  
    22512251<a href="#abnf.dependencies" class="smpl">Accept-Language</a> = &lt;Accept-Language, defined in [Part3], Section 5.4&gt;
    22522252<a href="#abnf.dependencies" class="smpl">Accept-Ranges</a> = &lt;Accept-Ranges, defined in [Part5], Section 5.1&gt;
    2253 <a href="#abnf.dependencies" class="smpl">Age</a> = &lt;Age, defined in [Part6], Section 15.1&gt;
     2253<a href="#abnf.dependencies" class="smpl">Age</a> = &lt;Age, defined in [Part6], Section 3.1&gt;
    22542254<a href="#header.allow" class="smpl">Allow</a> = "Allow:" OWS Allow-v
    22552255<a href="#header.allow" class="smpl">Allow-v</a> = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ]
    … …  
    23122312<a href="#header.user-agent" class="smpl">User-Agent-v</a> = product *( RWS ( product / comment ) )
    23132313
    2314 <a href="#abnf.dependencies" class="smpl">Vary</a> = &lt;Vary, defined in [Part6], Section 15.5&gt;
     2314<a href="#abnf.dependencies" class="smpl">Vary</a> = &lt;Vary, defined in [Part6], Section 3.5&gt;
    23152315
    23162316WWW-Authenticate =

  • draft-ietf-httpbis/latest-roy/p2-semantics.xml

    r500 r531  
    32133213<x:ref>Accept-Language</x:ref> = &lt;Accept-Language, defined in [Part3], Section 5.4&gt;
    32143214<x:ref>Accept-Ranges</x:ref> = &lt;Accept-Ranges, defined in [Part5], Section 5.1&gt;
    3215 <x:ref>Age</x:ref> = &lt;Age, defined in [Part6], Section 15.1&gt;
     3215<x:ref>Age</x:ref> = &lt;Age, defined in [Part6], Section 3.1&gt;
    32163216<x:ref>Allow</x:ref> = "Allow:" OWS Allow-v
    32173217<x:ref>Allow-v</x:ref> = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ]
    … …  
    32743274<x:ref>User-Agent-v</x:ref> = product *( RWS ( product / comment ) )
    32753275
    3276 <x:ref>Vary</x:ref> = &lt;Vary, defined in [Part6], Section 15.5&gt;
     3276<x:ref>Vary</x:ref> = &lt;Vary, defined in [Part6], Section 3.5&gt;
    32773277
    32783278WWW-Authenticate =

  • draft-ietf-httpbis/latest-roy/p3-payload.html

    r500 r531  
    379379      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
    380380      <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.424, 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/">
    382382      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    383383      <meta name="DC.Creator" content="Fielding, R.">
    … …  
    475475         <tr>
    476476            <td class="header left"></td>
    477             <td class="header right">March 4, 2009</td>
     477            <td class="header right">March 5, 2009</td>
    478478         </tr>
    479479      </table>
    … …  
    17491749<a href="#header.content-type" class="smpl">Content-Type-v</a> = media-type
    17501750
    1751 <a href="#abnf.dependencies" class="smpl">Expires</a> = &lt;Expires, defined in [Part6], Section 15.3&gt;
     1751<a href="#abnf.dependencies" class="smpl">Expires</a> = &lt;Expires, defined in [Part6], Section 3.3&gt;
    17521752
    17531753<a href="#abnf.dependencies" class="smpl">Last-Modified</a> = &lt;Last-Modified, defined in [Part4], Section 6.6&gt;

  • draft-ietf-httpbis/latest-roy/p3-payload.xml

    r500 r531  
    26672667<x:ref>Content-Type-v</x:ref> = media-type
    26682668
    2669 <x:ref>Expires</x:ref> = &lt;Expires, defined in [Part6], Section 15.3&gt;
     2669<x:ref>Expires</x:ref> = &lt;Expires, defined in [Part6], Section 3.3&gt;
    26702670
    26712671<x:ref>Last-Modified</x:ref> = &lt;Last-Modified, defined in [Part4], Section 6.6&gt;

  • draft-ietf-httpbis/latest-roy/p4-conditional.html

    r500 r531  
    368368      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    369369      <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.424, 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/">
    371371      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    372372      <meta name="DC.Creator" content="Fielding, R.">
    … …  
    464464         <tr>
    465465            <td class="header left"></td>
    466             <td class="header right">March 4, 2009</td>
     466            <td class="header right">March 5, 2009</td>
    467467         </tr>
    468468      </table>

  • draft-ietf-httpbis/latest-roy/p5-range.html

    r500 r531  
    368368      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
    369369      <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.424, 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/">
    371371      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    372372      <meta name="DC.Creator" content="Fielding, R.">
    … …  
    464464         <tr>
    465465            <td class="header left"></td>
    466             <td class="header right">March 4, 2009</td>
     466            <td class="header right">March 5, 2009</td>
    467467         </tr>
    468468      </table>

  • draft-ietf-httpbis/latest-roy/p6-cache.html

    r529 r531  
    687687</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="caching.overview" href="#caching.overview">Cache Operation</a></h1>
    688688      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<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">MAY</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:
    690690      </p>
    691691      <ul>
    … …  
    704704      </p>
    705705      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<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.
    707708      </p>
    708709      <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.
    709710      </p>
    710711      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<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">MAY</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:
    712713      </p>
    713714      <ul>
    … …  
    737738      <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&nbsp;2.5</a>.
    738739      </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.
    740742      </p>
    741743      <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>
    … …  
    749751         likely to change in a semantically significant way before the expiration time is reached.
    750752      </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 validate
    752          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>
    753755      <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
    754756         when they are not specified, employing algorithms that use other header values (such as the Last-Modified time) to estimate
    … …  
    783785      <h4 id="rfc.section.2.3.1.1"><a href="#rfc.section.2.3.1.1">2.3.1.1</a>&nbsp;<a id="heuristic.freshness" href="#heuristic.freshness">Calculating Heuristic Freshness</a></h4>
    784786      <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.
    786788      </p>
    787789      <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
    … …  
    840842         but is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
    841843      </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&nbsp;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
    846845         directive, a "must-revalidate" cache-response-directive, or an applicable "s-maxage" or "proxy-revalidate" cache-response-directive;
    847846         see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>).
    848847      </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&nbsp;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&nbsp;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&nbsp;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
    854854         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.
    855855      </p>
    … …  
    11391139      <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
    11401140      <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.
    11461147      </p>
    11471148      <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,
    … …  
    12541255  <a href="#header.warning" class="smpl">warn-text</a>  = <a href="#core.rules" class="smpl">quoted-string</a>
    12551256  <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.
    12581259      </p>
    12591260      <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
    … …  
    13191320      <p id="rfc.section.3.6.p.18">199 Miscellaneous warning </p>
    13201321      <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.
    13221323         </dd>
    13231324      </dl>
    … …  
    13311332      <p id="rfc.section.3.6.p.20">299 Miscellaneous persistent warning </p>
    13321333      <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.
    13341335         </dd>
    13351336      </dl>

  • draft-ietf-httpbis/latest-roy/p7-auth.html

    r501 r531  
    365365      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    366366      <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.424, 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/">
    368368      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    369369      <meta name="DC.Creator" content="Fielding, R.">
    … …  
    462462         <tr>
    463463            <td class="header left"></td>
    464             <td class="header right">March 4, 2009</td>
     464            <td class="header right">March 5, 2009</td>
    465465         </tr>
    466466      </table>
Note: See TracChangeset for help on using the changeset viewer.