Changeset 1692
- Timestamp:
- 23/06/12 12:01:38 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 13 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p0-introduction.html
- Property svn:eol-style set to native
- Property svn:mime-type set to text/html;charset=utf-8
r1689 r1692 374 374 } 375 375 @bottom-center { 376 content: "Expires December 2 4, 2012";376 content: "Expires December 25, 2012"; 377 377 } 378 378 @bottom-right { … … 405 405 <meta name="dct.creator" content="Reschke, J. F."> 406 406 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p0-introduction-latest"> 407 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 2">407 <meta name="dct.issued" scheme="ISO8601" content="2012-06-23"> 408 408 <meta name="dct.abstract" content="TODO"> 409 409 <meta name="description" content="TODO"> … … 425 425 </tr> 426 426 <tr> 427 <td class="left">Expires: December 2 4, 2012</td>427 <td class="left">Expires: December 25, 2012</td> 428 428 <td class="right">W3C</td> 429 429 </tr> … … 446 446 <tr> 447 447 <td class="left"></td> 448 <td class="right">June 2 2, 2012</td>448 <td class="right">June 23, 2012</td> 449 449 </tr> 450 450 </tbody> … … 469 469 in progress”. 470 470 </p> 471 <p>This Internet-Draft will expire on December 2 4, 2012.</p>471 <p>This Internet-Draft will expire on December 25, 2012.</p> 472 472 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 473 473 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p1-messaging.html
r1689 r1692 449 449 } 450 450 @bottom-center { 451 content: "Expires December 2 4, 2012";451 content: "Expires December 25, 2012"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 2">493 <meta name="dct.issued" scheme="ISO8601" content="2012-06-23"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: December 2 4, 2012</td>525 <td class="left">Expires: December 25, 2012</td> 526 526 <td class="right">greenbytes</td> 527 527 </tr> 528 528 <tr> 529 529 <td class="left"></td> 530 <td class="right">June 2 2, 2012</td>530 <td class="right">June 23, 2012</td> 531 531 </tr> 532 532 </tbody> … … 561 561 in progress”. 562 562 </p> 563 <p>This Internet-Draft will expire on December 2 4, 2012.</p>563 <p>This Internet-Draft will expire on December 25, 2012.</p> 564 564 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 565 565 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1689 r1692 16 16 <!ENTITY ID-YEAR "2012"> 17 17 <!ENTITY mdash "—"> 18 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> 18 19 <!ENTITY caching-overview "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 20 <!ENTITY cache-incomplete "<xref target='Part6' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 308 309 <x:note> 309 310 <t> 310 <x:h>Note:</x:h>The term 'user agent' covers both those situations where311 &Note; The term 'user agent' covers both those situations where 311 312 there is a user (human) interacting with the software agent (and for which 312 313 user interface or interactive suggestions might be made, e.g., warning the … … 1187 1188 <x:note> 1188 1189 <t> 1189 <x:h>Note:</x:h>The "Set-Cookie" header field as implemented in1190 &Note; The "Set-Cookie" header field as implemented in 1190 1191 practice can occur multiple times, but does not use the list syntax, and 1191 1192 thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/> … … 1978 1979 </t> 1979 1980 <x:note><t> 1980 <x:h>Note:</x:h>Use of program names for the identification of encoding formats1981 &Note; Use of program names for the identification of encoding formats 1981 1982 is not desirable and is discouraged for future encodings. Their 1982 1983 use here is representative of historical practice, not good … … 1984 1985 </t></x:note> 1985 1986 <x:note><t> 1986 <x:h>Note:</x:h>For compatibility with previous implementations of HTTP,1987 &Note; For compatibility with previous implementations of HTTP, 1987 1988 applications &SHOULD; consider "x-gzip" and "x-compress" to be 1988 1989 equivalent to "gzip" and "compress" respectively. … … 2009 2010 <x:note> 2010 2011 <t> 2011 <x:h>Note:</x:h>Some incorrect implementations send the "deflate"2012 &Note; Some incorrect implementations send the "deflate" 2012 2013 compressed data without the zlib wrapper. 2013 2014 </t> … … 2084 2085 response on behalf of downstream recipients. 2085 2086 </t><t> 2086 <x:h>Note:</x:h>HTTP/1.1 does not define any means to limit the size of a2087 &Note; HTTP/1.1 does not define any means to limit the size of a 2087 2088 chunked response such that a client can be assured of buffering 2088 2089 the entire response.</t> … … 2128 2129 <x:note> 2129 2130 <t> 2130 <x:h>Note:</x:h>"Quality values" is a misnomer, since these values merely represent2131 &Note; "Quality values" is a misnomer, since these values merely represent 2131 2132 relative degradation in desired quality. 2132 2133 </t> -
draft-ietf-httpbis/latest/p2-semantics.html
r1689 r1692 449 449 } 450 450 @bottom-center { 451 content: "Expires December 2 4, 2012";451 content: "Expires December 25, 2012"; 452 452 } 453 453 @bottom-right { … … 497 497 <meta name="dct.creator" content="Reschke, J. F."> 498 498 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 499 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 2">499 <meta name="dct.issued" scheme="ISO8601" content="2012-06-23"> 500 500 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 501 501 <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 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation."> … … 528 528 </tr> 529 529 <tr> 530 <td class="left">Expires: December 2 4, 2012</td>530 <td class="left">Expires: December 25, 2012</td> 531 531 <td class="right">greenbytes</td> 532 532 </tr> 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">June 2 2, 2012</td>535 <td class="right">June 23, 2012</td> 536 536 </tr> 537 537 </tbody> … … 563 563 in progress”. 564 564 </p> 565 <p>This Internet-Draft will expire on December 2 4, 2012.</p>565 <p>This Internet-Draft will expire on December 25, 2012.</p> 566 566 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 567 567 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1689 r1692 16 16 <!ENTITY ID-YEAR "2012"> 17 17 <!ENTITY mdash "—"> 18 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> 18 19 <!ENTITY architecture "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 20 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1542 1543 <x:note> 1543 1544 <t> 1544 <x:h>Note:</x:h>In HTTP/1.0, only the status codes 301 (Moved Permanently)1545 &Note; In HTTP/1.0, only the status codes 301 (Moved Permanently) 1545 1546 and 302 (Found) were defined for the first type of redirect, and the second 1546 1547 type did not exist at all (<xref target="RFC1945" x:fmt="," x:sec="9.3"/>). … … 1573 1574 <x:note> 1574 1575 <t> 1575 <x:h>Note:</x:h>An earlier version of this specification recommended a1576 &Note; An earlier version of this specification recommended a 1576 1577 maximum of five redirections (<xref target="RFC2068" x:fmt="," x:sec="10.3"/>). 1577 1578 Content developers need to be aware that some clients might … … 1633 1634 <x:note> 1634 1635 <t> 1635 <x:h>Note:</x:h>For historic reasons, user agents &MAY; change the1636 &Note; For historic reasons, user agents &MAY; change the 1636 1637 request method from POST to GET for the subsequent request. If this 1637 1638 behavior is undesired, status code 307 (Temporary Redirect) can be used … … 1656 1657 <x:note> 1657 1658 <t> 1658 <x:h>Note:</x:h>For historic reasons, user agents &MAY; change the1659 &Note; For historic reasons, user agents &MAY; change the 1659 1660 request method from POST to GET for the subsequent request. If this 1660 1661 behavior is undesired, status code 307 (Temporary Redirect) can be used … … 1739 1740 <x:note> 1740 1741 <t> 1741 <x:h>Note:</x:h>This status code is similar to 302 Found, except that1742 &Note; This status code is similar to 302 Found, except that 1742 1743 it does not allow rewriting the request method from POST to GET. This 1743 1744 specification defines no equivalent counterpart for 301 Moved Permanently … … 1838 1839 <x:note> 1839 1840 <t> 1840 <x:h>Note:</x:h>HTTP/1.1 servers are allowed to return responses which are1841 &Note; HTTP/1.1 servers are allowed to return responses which are 1841 1842 not acceptable according to the accept header fields sent in the 1842 1843 request. In some cases, this might even be preferable to sending a … … 2063 2064 <x:note> 2064 2065 <t> 2065 <x:h>Note:</x:h>The existence of the 503 status code does not imply that a2066 &Note; The existence of the 503 status code does not imply that a 2066 2067 server has to use it when becoming overloaded. Some servers might wish 2067 2068 to simply refuse the connection. … … 2234 2235 <x:note> 2235 2236 <t> 2236 <x:h>Note:</x:h>Recipients of date values are encouraged to be robust in2237 &Note; Recipients of date values are encouraged to be robust in 2237 2238 accepting date values that might have been sent by non-HTTP 2238 2239 applications, as is sometimes the case when retrieving or posting … … 2242 2243 <x:note> 2243 2244 <t> 2244 <x:h>Note:</x:h>HTTP requirements for the date/time stamp format apply only2245 &Note; HTTP requirements for the date/time stamp format apply only 2245 2246 to their usage within the protocol stream. Clients and servers are 2246 2247 not required to use these formats for user presentation, request … … 2500 2501 <x:note> 2501 2502 <t> 2502 <x:h>Note:</x:h>The "multipart/form-data" type has been specifically defined2503 &Note; The "multipart/form-data" type has been specifically defined 2503 2504 for carrying form data suitable for processing via the POST 2504 2505 request method, as described in <xref target="RFC2388"/>. … … 2867 2868 <x:note> 2868 2869 <t> 2869 <x:h>Note:</x:h>In practice, User-Agent based negotiation is fragile,2870 &Note; In practice, User-Agent based negotiation is fragile, 2870 2871 because new clients might not be recognized. 2871 2872 </t> … … 2962 2963 <x:note> 2963 2964 <t> 2964 <x:h>Note:</x:h>Use of the "q" parameter name to separate media type2965 &Note; Use of the "q" parameter name to separate media type 2965 2966 parameters from Accept extension parameters is due to historical 2966 2967 practice. Although this prevents any media type parameter named … … 3044 3045 </texttable> 3045 3046 <t> 3046 <x:h>Note:</x:h>A user agent might be provided with a default set of quality3047 3048 3049 3047 &Note; A user agent might be provided with a default set of quality 3048 values for certain media ranges. However, unless the user agent is 3049 a closed system which cannot interact with other rendering agents, 3050 this default set ought to be configurable by the user. 3050 3051 </t> 3051 3052 </section> … … 3161 3162 <x:note> 3162 3163 <t> 3163 <x:h>Note:</x:h>Most HTTP/1.0 applications do not recognize or obey qvalues3164 &Note; Most HTTP/1.0 applications do not recognize or obey qvalues 3164 3165 associated with content-codings. This means that qvalues will not 3165 3166 work and are not permitted with x-gzip or x-compress. … … 3205 3206 <x:note> 3206 3207 <t> 3207 <x:h>Note:</x:h>The "Basic Filtering" scheme (<xref target="RFC4647"3208 &Note; The "Basic Filtering" scheme (<xref target="RFC4647" 3208 3209 x:fmt="," x:sec="3.3.1"/>) is identical to the matching scheme that was 3209 3210 previously defined in <xref target="RFC2616" x:fmt="of" x:sec="14.4"/>. … … 3225 3226 <x:note> 3226 3227 <t> 3227 <x:h>Note:</x:h>When making the choice of linguistic preference available to3228 &Note; When making the choice of linguistic preference available to 3228 3229 the user, we remind implementors of the fact that users are not 3229 3230 familiar with the details of language matching as described above, … … 3693 3694 <x:note> 3694 3695 <t> 3695 <x:h>Note:</x:h>Some recipients attempt to recover from Location fields3696 &Note; Some recipients attempt to recover from Location fields 3696 3697 that are not valid URI references. This specification does not mandate or 3697 3698 define such processing, but does allow it (see <xref target="intro.conformance.and.error.handling"/>). … … 3706 3707 <x:note> 3707 3708 <t> 3708 <x:h>Note:</x:h>The Content-Location header field (&header-content-location;) differs3709 &Note; The Content-Location header field (&header-content-location;) differs 3709 3710 from Location in that the Content-Location identifies the most specific 3710 3711 resource corresponding to the enclosed representation. … … 3856 3857 <x:note> 3857 3858 <t> 3858 <x:h>Note:</x:h>Revealing the specific software version of the server might3859 &Note; Revealing the specific software version of the server might 3859 3860 allow the server machine to become more vulnerable to attacks 3860 3861 against software that is known to contain security holes. Server -
draft-ietf-httpbis/latest/p3-payload.html
r1689 r1692 374 374 } 375 375 @bottom-center { 376 content: "Expires December 2 4, 2012";376 content: "Expires December 25, 2012"; 377 377 } 378 378 @bottom-right { … … 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 2">406 <meta name="dct.issued" scheme="ISO8601" content="2012-06-23"> 407 407 <meta name="dct.abstract" content="This part is now obsolete. Please see HTTPbis, Part 2."> 408 408 <meta name="description" content="This part is now obsolete. Please see HTTPbis, Part 2."> … … 424 424 </tr> 425 425 <tr> 426 <td class="left">Expires: December 2 4, 2012</td>426 <td class="left">Expires: December 25, 2012</td> 427 427 <td class="right">W3C</td> 428 428 </tr> … … 437 437 <tr> 438 438 <td class="left"></td> 439 <td class="right">June 2 2, 2012</td>439 <td class="right">June 23, 2012</td> 440 440 </tr> 441 441 </tbody> … … 453 453 in progress”. 454 454 </p> 455 <p>This Internet-Draft will expire on December 2 4, 2012.</p>455 <p>This Internet-Draft will expire on December 25, 2012.</p> 456 456 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 457 457 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1691 r1692 15 15 <!ENTITY ID-MONTH "June"> 16 16 <!ENTITY ID-YEAR "2012"> 17 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> 17 18 <!ENTITY architecture "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 19 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 484 485 <x:note> 485 486 <t> 486 <x:h>Note:</x:h>Previously, opaque-tag was defined to be a quoted-string487 &Note; Previously, opaque-tag was defined to be a quoted-string 487 488 (<xref target="RFC2616" x:fmt="," x:sec="3.11"/>), thus some recipients 488 489 might perform backslash unescaping. Servers therefore ought to avoid … … 635 636 <x:note> 636 637 <t> 637 <x:h>Note:</x:h>Content codings are a property of the representation,638 &Note; Content codings are a property of the representation, 638 639 so therefore an entity-tag of an encoded representation has to be distinct 639 640 from an unencoded representation to prevent conflicts during cache updates … … 706 707 conditional header fields in the request. 707 708 <list><t> 708 <x:h>Note:</x:h>The general principle behind these rules is that HTTP/1.1709 &Note; The general principle behind these rules is that HTTP/1.1 709 710 servers and clients ought to transmit as much non-redundant 710 711 information as is available in their responses and requests. … … 897 898 information with a minimum amount of transaction overhead. 898 899 <list><t> 899 <x:h>Note:</x:h>The Range header field modifies the meaning of If-Modified-Since;900 &Note; The Range header field modifies the meaning of If-Modified-Since; 900 901 see &header-range; for full details. 901 902 </t><t> 902 <x:h>Note:</x:h>If-Modified-Since times are interpreted by the server, whose903 &Note; If-Modified-Since times are interpreted by the server, whose 903 904 clock might not be synchronized with the client. 904 905 </t><t> 905 <x:h>Note:</x:h>When handling an If-Modified-Since header field, some906 &Note; When handling an If-Modified-Since header field, some 906 907 servers will use an exact date comparison function, rather than a 907 908 less-than function, for deciding whether to send a 304 (Not … … 911 912 header field whenever possible. 912 913 </t><t> 913 <x:h>Note:</x:h>If a client uses an arbitrary date in the If-Modified-Since914 &Note; If a client uses an arbitrary date in the If-Modified-Since 914 915 header field instead of a date taken from the Last-Modified header field for 915 916 the same request, the client needs to be aware that this -
draft-ietf-httpbis/latest/p5-range.html
r1689 r1692 449 449 } 450 450 @bottom-center { 451 content: "Expires December 2 4, 2012";451 content: "Expires December 25, 2012"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 2">494 <meta name="dct.issued" scheme="ISO8601" content="2012-06-23"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 496 496 <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 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range requests and the rules for constructing and combining responses to those requests."> … … 518 518 </tr> 519 519 <tr> 520 <td class="left">Expires: December 2 4, 2012</td>520 <td class="left">Expires: December 25, 2012</td> 521 521 <td class="right">J. Reschke, Editor</td> 522 522 </tr> … … 527 527 <tr> 528 528 <td class="left"></td> 529 <td class="right">June 2 2, 2012</td>529 <td class="right">June 23, 2012</td> 530 530 </tr> 531 531 </tbody> … … 555 555 in progress”. 556 556 </p> 557 <p>This Internet-Draft will expire on December 2 4, 2012.</p>557 <p>This Internet-Draft will expire on December 25, 2012.</p> 558 558 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 559 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p5-range.xml
r1689 r1692 15 15 <!ENTITY ID-MONTH "June"> 16 16 <!ENTITY ID-YEAR "2012"> 17 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> 17 18 <!ENTITY architecture "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 19 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 376 377 <x:note> 377 378 <t> 378 <x:h>Note:</x:h>Clients cannot depend on servers to send a 416 (Requested379 &Note; Clients cannot depend on servers to send a 416 (Requested 379 380 range not satisfiable) response instead of a 200 (OK) response for 380 381 an unsatisfiable Range header field, since not all servers … … 1228 1229 <x:note> 1229 1230 <t> 1230 <x:h>Note:</x:h>Despite the name "multipart/byteranges" is not limited to the byte ranges only.1231 &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only. 1231 1232 </t> 1232 1233 </x:note> -
draft-ietf-httpbis/latest/p6-cache.html
r1689 r1692 452 452 } 453 453 @bottom-center { 454 content: "Expires December 2 4, 2012";454 content: "Expires December 25, 2012"; 455 455 } 456 456 @bottom-right { … … 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 2">496 <meta name="dct.issued" scheme="ISO8601" content="2012-06-23"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <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."> … … 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: December 2 4, 2012</td>522 <td class="left">Expires: December 25, 2012</td> 523 523 <td class="right">M. Nottingham, Editor</td> 524 524 </tr> … … 537 537 <tr> 538 538 <td class="left"></td> 539 <td class="right">June 2 2, 2012</td>539 <td class="right">June 23, 2012</td> 540 540 </tr> 541 541 </tbody> … … 567 567 in progress”. 568 568 </p> 569 <p>This Internet-Draft will expire on December 2 4, 2012.</p>569 <p>This Internet-Draft will expire on December 25, 2012.</p> 570 570 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 571 571 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 923 923 </pre> <p id="rfc.section.2.3.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>. 924 924 </p> 925 <p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation -- either constraining it relaxing it --by using the max-age and925 <p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation — either constraining it relaxing it — by using the max-age and 926 926 min-fresh request cache directives. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a> for details. 927 927 </p> … … 1326 1326 case-insensitive. 1327 1327 </li> 1328 <li> 1328 <li><b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message 1329 1329 content. Also, private response directives with field-names are often handled by implementations as if an unqualified private 1330 1330 directive was received; i.e., the special handling for the qualified form is not widely implemented. … … 1345 1345 case-insensitive. 1346 1346 </li> 1347 <li> 1347 <li><b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often 1348 1348 handled by implementations as if an unqualified no-cache directive was received; i.e., the special handling for the qualified 1349 1349 form is not widely implemented. -
draft-ietf-httpbis/latest/p6-cache.xml
r1689 r1692 15 15 <!ENTITY ID-MONTH "June"> 16 16 <!ENTITY ID-YEAR "2012"> 17 <!ENTITY mdash "—"> 18 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> 17 19 <!ENTITY architecture "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 20 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 635 637 </t> 636 638 <t> 637 Additionally, clients can influence freshness calculation --either638 constraining it relaxing it --by using the max-age and min-fresh639 Additionally, clients can influence freshness calculation — either 640 constraining it relaxing it — by using the max-age and min-fresh 639 641 request cache directives. See <xref target="cache-request-directive" /> 640 642 for details. … … 694 696 <x:note> 695 697 <t> 696 <x:h>Note:</x:h>RFC 2616 (<xref target="RFC2616" x:fmt=","698 &Note; RFC 2616 (<xref target="RFC2616" x:fmt="," 697 699 x:sec="13.9"/>) required that caches do not calculate heuristic 698 700 freshness for URIs with query components (i.e., those containing '?'). … … 1201 1203 <x:note> 1202 1204 <t> 1203 <x:h>Note:</x:h>HTTP/1.0 caches might not implement Cache-Control and1205 &Note; HTTP/1.0 caches might not implement Cache-Control and 1204 1206 might only implement Pragma: no-cache (see <xref target="header.pragma" 1205 1207 />). … … 1379 1381 fields defined by this specification. Field names are case-insensitive. 1380 1382 </t> 1381 <t> <x:h>Note:</x:h>This usage of the word "private" only controls1383 <t>&Note; This usage of the word "private" only controls 1382 1384 where the response can be stored; it cannot ensure the privacy of the 1383 1385 message content. Also, private response directives with field-names are … … 1408 1410 fields defined by this specification. Field names are case-insensitive. 1409 1411 </t> 1410 <t> <x:h>Note:</x:h>Most HTTP/1.0 caches will not recognize or obey1412 <t>&Note; Most HTTP/1.0 caches will not recognize or obey 1411 1413 this directive. Also, no-cache response directives with field-names are 1412 1414 often handled by implementations as if an unqualified no-cache directive … … 1598 1600 <x:note> 1599 1601 <t> 1600 <x:h>Note:</x:h>If a response includes a Cache-Control field with the1602 &Note; If a response includes a Cache-Control field with the 1601 1603 max-age directive (see <xref target="cache-response-directive" />), 1602 1604 that directive overrides the Expires field. Likewise, the s-maxage … … 1674 1676 <x:note> 1675 1677 <t> 1676 <x:h>Note:</x:h>Because the meaning of "Pragma: no-cache" in responses is not1678 &Note; Because the meaning of "Pragma: no-cache" in responses is not 1677 1679 specified, it does not provide a reliable replacement for 1678 1680 "Cache-Control: no-cache" in them. -
draft-ietf-httpbis/latest/p7-auth.html
r1689 r1692 449 449 } 450 450 @bottom-center { 451 content: "Expires December 2 4, 2012";451 content: "Expires December 25, 2012"; 452 452 } 453 453 @bottom-right { … … 489 489 <meta name="dct.creator" content="Reschke, J. F."> 490 490 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 491 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 2">491 <meta name="dct.issued" scheme="ISO8601" content="2012-06-23"> 492 492 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 493 493 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework."> … … 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: December 2 4, 2012</td>522 <td class="left">Expires: December 25, 2012</td> 523 523 <td class="right">greenbytes</td> 524 524 </tr> 525 525 <tr> 526 526 <td class="left"></td> 527 <td class="right">June 2 2, 2012</td>527 <td class="right">June 23, 2012</td> 528 528 </tr> 529 529 </tbody> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on December 2 4, 2012.</p>555 <p>This Internet-Draft will expire on December 25, 2012.</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> … … 784 784 can use a generic parser that applies to all authentication schemes. 785 785 </p> 786 <p> <b>Note:</b> the fact that the value syntax for the "realm" parameter is restricted to quoted-string was a bad design choice not to be786 <p> <b>Note:</b> The fact that the value syntax for the "realm" parameter is restricted to quoted-string was a bad design choice not to be 787 787 repeated for new parameters. 788 788 </p> -
draft-ietf-httpbis/latest/p7-auth.xml
r1689 r1692 16 16 <!ENTITY ID-YEAR "2012"> 17 17 <!ENTITY mdash "—"> 18 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> 18 19 <!ENTITY architecture "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 20 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 272 273 <x:note> 273 274 <t> 274 <x:h>Note:</x:h>User agents will need to take special care in parsing the275 &Note; User agents will need to take special care in parsing the 275 276 WWW-Authenticate and Proxy-Authenticate header field values because they 276 277 can contain more than one challenge, or if more than one of each is … … 281 282 <x:note> 282 283 <t> 283 <x:h>Note:</x:h>Many clients fail to parse challenges containing unknown284 &Note; Many clients fail to parse challenges containing unknown 284 285 schemes. A workaround for this problem is to list well-supported schemes 285 286 (such as "basic") first.<!-- see http://greenbytes.de/tech/tc/httpauth/#multibasicunknown2 --> … … 447 448 </t> 448 449 <t> 449 <x:h>Note:</x:h> the fact that the value syntax for the "realm" parameter450 &Note; The fact that the value syntax for the "realm" parameter 450 451 is restricted to quoted-string was a bad design choice not to be repeated 451 452 for new parameters. … … 675 676 <x:note> 676 677 <t> 677 <x:h>Note:</x:h>The challenge grammar production uses the list syntax as678 &Note; The challenge grammar production uses the list syntax as 678 679 well. Therefore, a sequence of comma, whitespace, and comma can be 679 680 considered both as applying to the preceding challenge, or to be an
Note: See TracChangeset
for help on using the changeset viewer.