Changeset 2073
- Timestamp:
- 31/12/12 11:02:54 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2072 r2073 2098 2098 <p id="rfc.section.5.5.3.p.1">The "User-Agent" header field contains information about the user agent originating the request, which is often used by servers 2099 2099 to help identify the scope of reported interoperability problems, to work around or tailor responses to avoid particular user 2100 agent limitations, and for analytics regarding browser or operating system use. A user agent <em class="bcp14">SHOULD</em> includea User-Agent field in each request unless specifically configured not to do so.2100 agent limitations, and for analytics regarding browser or operating system use. A user agent <em class="bcp14">SHOULD</em> send a User-Agent field in each request unless specifically configured not to do so. 2101 2101 </p> 2102 2102 <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.36"></span> <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#header.user-agent" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#header.user-agent" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) ) … … 2726 2726 <div id="rfc.iref.s.6"></div> 2727 2727 <p id="rfc.section.6.6.p.1">The <dfn>5xx (Server Error)</dfn> class of status code indicates that the server is aware that it has erred or is incapable of performing the requested method. 2728 Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> includea representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.2728 Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition. 2729 2729 User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method. 2730 2730 </p> … … 2813 2813 </pre><p id="rfc.section.7.1.1.1.p.5">HTTP/1.1 clients and servers that parse a 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. 2814 2814 </p> 2815 <p id="rfc.section.7.1.1.1.p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated 2816 Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for 2817 time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar. 2815 <p id="rfc.section.7.1.1.1.p.6">All HTTP date/time stamps are represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is 2816 exactly equal to UTC (Coordinated Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as 2817 the three-letter abbreviation for time zone, and is assumed when reading the asctime format. HTTP-date is case sensitive. 2818 A sender <em class="bcp14">MUST NOT</em> generate additional whitespace in an HTTP-date beyond that specifically included as SP in the grammar. 2818 2819 </p> 2819 2820 <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.39"></span> <a href="#http.date" class="smpl">HTTP-date</a> = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2072 r2073 2439 2439 the scope of reported interoperability problems, to work around or tailor 2440 2440 responses to avoid particular user agent limitations, and for analytics 2441 regarding browser or operating system use. A user agent &SHOULD; include2441 regarding browser or operating system use. A user agent &SHOULD; send 2442 2442 a User-Agent field in each request unless specifically configured not 2443 2443 to do so. … … 3389 3389 <t> 3390 3390 The <x:dfn>5xx (Server Error)</x:dfn> class of status code indicates that 3391 the server is aware that it has erred or is incapable of 3392 performing the requested method. Except when responding to a HEAD request, the 3393 server &SHOULD; include a representation containing an explanation of the 3394 error situation, and whether it is a temporary or permanent 3395 condition. User agents &SHOULD; display any included representation to the 3396 user. These response codes are applicable to any request method. 3391 the server is aware that it has erred or is incapable of performing the 3392 requested method. 3393 Except when responding to a HEAD request, the server &SHOULD; send a 3394 representation containing an explanation of the error situation, and 3395 whether it is a temporary or permanent condition. 3396 User agents &SHOULD; display any included representation to the user. 3397 These response codes are applicable to any request method. 3397 3398 </t> 3398 3399 … … 3532 3533 </t> 3533 3534 <t> 3534 All HTTP date/time stamps &MUST; be represented in Greenwich Mean Time3535 All HTTP date/time stamps are represented in Greenwich Mean Time 3535 3536 (GMT), without exception. For the purposes of HTTP, GMT is exactly 3536 3537 equal to UTC (Coordinated Universal Time). This is indicated in the 3537 3538 first two formats by the inclusion of "GMT" as the three-letter 3538 abbreviation for time zone, and &MUST; beassumed when reading the3539 asctime format. HTTP-date is case sensitive and &MUST-NOT; include3540 additional whitespace beyond that specifically included as SP in the3541 grammar.3539 abbreviation for time zone, and is assumed when reading the 3540 asctime format. HTTP-date is case sensitive. A sender &MUST-NOT; generate 3541 additional whitespace in an HTTP-date beyond that specifically included as 3542 SP in the grammar. 3542 3543 </t> 3543 3544 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-date"/> -
draft-ietf-httpbis/latest/p5-range.html
r2069 r2073 449 449 } 450 450 @bottom-center { 451 content: "Expires July 3, 2013";451 content: "Expires July 4, 2013"; 452 452 } 453 453 @bottom-right { … … 493 493 <meta name="dct.creator" content="Reschke, J. F."> 494 494 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 495 <meta name="dct.issued" scheme="ISO8601" content="2012-12-3 0">495 <meta name="dct.issued" scheme="ISO8601" content="2012-12-31"> 496 496 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 497 497 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests."> … … 519 519 </tr> 520 520 <tr> 521 <td class="left">Expires: July 3, 2013</td>521 <td class="left">Expires: July 4, 2013</td> 522 522 <td class="right">J. Reschke, Editor</td> 523 523 </tr> … … 528 528 <tr> 529 529 <td class="left"></td> 530 <td class="right">December 3 0, 2012</td>530 <td class="right">December 31, 2012</td> 531 531 </tr> 532 532 </tbody> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on July 3, 2013.</p>555 <p>This Internet-Draft will expire on July 4, 2013.</p> 556 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 557 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 803 803 </p> 804 804 <p id="rfc.section.5.2.p.7">In the case of a byte range request: a server sending a response with status code <a href="#status.416" class="smpl">416 (Requested Range Not 805 Satisfiable)</a> <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the806 selected resource. A response with status code <a href="#status.206" class="smpl">206 (Partial Content)</a> <em class="bcp14">MUST NOT</em> includea Content-Range field with a byte-range-resp-spec of "*".805 Satisfiable)</a> <em class="bcp14">SHOULD</em> send a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the selected 806 resource. A response with status code <a href="#status.206" class="smpl">206 (Partial Content)</a> <em class="bcp14">MUST NOT</em> send a Content-Range field with a byte-range-resp-spec of "*". 807 807 </p> 808 808 <p id="rfc.section.5.2.p.8">The "Content-Range" header field has no meaning for status codes that do not explicitly describe its semantic. Currently, -
draft-ietf-httpbis/latest/p5-range.xml
r2069 r2073 522 522 In the case of a byte range request: 523 523 a server sending a response with status code <x:ref>416 (Requested Range Not 524 Satisfiable)</x:ref> &SHOULD; includea Content-Range field with a byte-range-resp-spec524 Satisfiable)</x:ref> &SHOULD; send a Content-Range field with a byte-range-resp-spec 525 525 of "*". The instance-length specifies the current length of 526 526 the selected resource. A response with status code <x:ref>206 (Partial Content)</x:ref> 527 &MUST-NOT; includea Content-Range field with a byte-range-resp-spec of "*".527 &MUST-NOT; send a Content-Range field with a byte-range-resp-spec of "*". 528 528 </t> 529 529 <t> -
draft-ietf-httpbis/latest/p6-cache.html
r2069 r2073 452 452 } 453 453 @bottom-center { 454 content: "Expires July 3, 2013";454 content: "Expires July 4, 2013"; 455 455 } 456 456 @bottom-right { … … 498 498 <meta name="dct.creator" content="Reschke, J. F."> 499 499 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 500 <meta name="dct.issued" scheme="ISO8601" content="2012-12-3 0">500 <meta name="dct.issued" scheme="ISO8601" content="2012-12-31"> 501 501 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 502 502 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: July 3, 2013</td>526 <td class="left">Expires: July 4, 2013</td> 527 527 <td class="right">J. Reschke, Editor</td> 528 528 </tr> … … 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">December 3 0, 2012</td>535 <td class="right">December 31, 2012</td> 536 536 </tr> 537 537 </tbody> … … 559 559 in progress”. 560 560 </p> 561 <p>This Internet-Draft will expire on July 3, 2013.</p>561 <p>This Internet-Draft will expire on July 4, 2013.</p> 562 562 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 563 563 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1524 1524 <div id="rfc.iref.52"></div> 1525 1525 <h3 id="rfc.section.7.5.1"><a href="#rfc.section.7.5.1">7.5.1</a> <a id="warn.110" href="#warn.110">110 Response is Stale</a></h3> 1526 <p id="rfc.section.7.5.1.p.1">A cache <em class="bcp14">SHOULD</em> include this whenever the sent response is stale.1526 <p id="rfc.section.7.5.1.p.1">A cache <em class="bcp14">SHOULD</em> generate this whenever the sent response is stale. 1527 1527 </p> 1528 1528 <div id="rfc.iref.52"></div> 1529 1529 <h3 id="rfc.section.7.5.2"><a href="#rfc.section.7.5.2">7.5.2</a> <a id="warn.111" href="#warn.111">111 Revalidation Failed</a></h3> 1530 <p id="rfc.section.7.5.2.p.1">A cache <em class="bcp14">SHOULD</em> include this when sending a stale response because an attempt to validate the response failed, due to an inability to reach1530 <p id="rfc.section.7.5.2.p.1">A cache <em class="bcp14">SHOULD</em> generate this when sending a stale response because an attempt to validate the response failed, due to an inability to reach 1531 1531 the server. 1532 1532 </p> 1533 1533 <div id="rfc.iref.52"></div> 1534 1534 <h3 id="rfc.section.7.5.3"><a href="#rfc.section.7.5.3">7.5.3</a> <a id="warn.112" href="#warn.112">112 Disconnected Operation</a></h3> 1535 <p id="rfc.section.7.5.3.p.1">A cache <em class="bcp14">SHOULD</em> include this if it is intentionally disconnected from the rest of the network for a period of time.1535 <p id="rfc.section.7.5.3.p.1">A cache <em class="bcp14">SHOULD</em> generate this if it is intentionally disconnected from the rest of the network for a period of time. 1536 1536 </p> 1537 1537 <div id="rfc.iref.52"></div> 1538 1538 <h3 id="rfc.section.7.5.4"><a href="#rfc.section.7.5.4">7.5.4</a> <a id="warn.113" href="#warn.113">113 Heuristic Expiration</a></h3> 1539 <p id="rfc.section.7.5.4.p.1">A cache <em class="bcp14">SHOULD</em> include this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 241540 hours.1539 <p id="rfc.section.7.5.4.p.1">A cache <em class="bcp14">SHOULD</em> generate this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 1540 24 hours. 1541 1541 </p> 1542 1542 <div id="rfc.iref.52"></div> -
draft-ietf-httpbis/latest/p6-cache.xml
r2069 r2073 1783 1783 <iref primary="true" item="110 Response is Stale (warn code)" x:for-anchor=""/> 1784 1784 <t> 1785 A cache &SHOULD; include this whenever the sent response is stale.1785 A cache &SHOULD; generate this whenever the sent response is stale. 1786 1786 </t> 1787 1787 </section> … … 1790 1790 <iref primary="true" item="111 Revalidation Failed (warn code)" x:for-anchor=""/> 1791 1791 <t> 1792 A cache &SHOULD; include this when sending a stale response because an1792 A cache &SHOULD; generate this when sending a stale response because an 1793 1793 attempt to validate the response failed, due to an inability to reach 1794 1794 the server. … … 1799 1799 <iref primary="true" item="112 Disconnected Operation (warn code)" x:for-anchor=""/> 1800 1800 <t> 1801 A cache &SHOULD; include this if it is intentionally disconnected from1801 A cache &SHOULD; generate this if it is intentionally disconnected from 1802 1802 the rest of the network for a period of time. 1803 1803 </t> … … 1807 1807 <iref primary="true" item="113 Heuristic Expiration (warn code)" x:for-anchor=""/> 1808 1808 <t> 1809 A cache &SHOULD; include this if it heuristically chose a freshness1809 A cache &SHOULD; generate this if it heuristically chose a freshness 1810 1810 lifetime greater than 24 hours and the response's age is greater than 24 1811 1811 hours.
Note: See TracChangeset
for help on using the changeset viewer.