Changeset 1809 for draft-ietf-httpbis/20
- Timestamp:
- 16/07/12 16:42:58 (11 years ago)
- Location:
- draft-ietf-httpbis/20
- Files:
-
- 13 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/20
-
Property
svn:mergeinfo
set to
/draft-ietf-httpbis/latest merged eligible
-
Property
svn:mergeinfo
set to
-
draft-ietf-httpbis/20/draft-ietf-httpbis-p5-range-20.txt
r1807 r1809 18 18 The Hypertext Transfer Protocol (HTTP) is an application-level 19 19 protocol for distributed, collaborative, hypertext information 20 systems. HTTP has been in use by the World Wide Web global 21 information initiative since 1990. This document is Part 5 of the 22 seven-part specification that defines the protocol referred to as 23 "HTTP/1.1" and, taken together, obsoletes RFC 2616. 24 25 Part 5 defines range requests and the rules for constructing and 26 combining responses to those requests. 20 systems. This document defines range requests and the rules for 21 constructing and combining responses to those requests. 27 22 28 23 Editorial Note (To be removed by RFC Editor) … … 50 45 51 46 Internet-Drafts are draft documents valid for a maximum of six months 52 53 54 55 Fielding, et al. Expires January 17, 2013 [Page 1]56 57 58 Internet-Draft HTTP/1.1, Part 5 July 201259 60 61 47 and may be updated, replaced, or obsoleted by other documents at any 62 48 time. It is inappropriate to use Internet-Drafts as reference … … 64 50 65 51 This Internet-Draft will expire on January 17, 2013. 52 53 54 55 Fielding, et al. Expires January 17, 2013 [Page 1] 56 57 58 Internet-Draft HTTP/1.1, Part 5 July 2012 59 66 60 67 61 Copyright Notice … … 91 85 it for publication as an RFC or to translate it into languages other 92 86 than English. 87 88 89 90 91 92 93 93 94 94 -
draft-ietf-httpbis/20/draft-ietf-httpbis-p5-range-20.xml
r1807 r1809 75 75 <t> 76 76 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 77 distributed, collaborative, hypertext information systems. HTTP has been in 78 use by the World Wide Web global information initiative since 1990. This 79 document is Part 5 of the seven-part specification that defines the protocol 80 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 81 </t> 82 <t> 83 Part 5 defines range requests and the rules for constructing and 84 combining responses to those requests. 77 distributed, collaborative, hypertext information systems. This document 78 defines range requests and the rules for constructing and combining 79 responses to those requests. 85 80 </t> 86 81 </abstract> -
draft-ietf-httpbis/20/draft-ietf-httpbis-p6-cache-20.txt
r1807 r1809 20 20 The Hypertext Transfer Protocol (HTTP) is an application-level 21 21 protocol for distributed, collaborative, hypertext information 22 systems. HTTP has been in use by the World Wide Web global 23 information initiative since 1990. This document is Part 6 of the 24 seven-part specification that defines the protocol referred to as 25 "HTTP/1.1" and, taken together, obsoletes RFC 2616. 26 27 Part 6 defines requirements on HTTP caches and the associated header 28 fields that control cache behavior or indicate cacheable response 29 messages. 22 systems. This document defines requirements on HTTP caches and the 23 associated header fields that control cache behavior or indicate 24 cacheable response messages. 30 25 31 26 Editorial Note (To be removed by RFC Editor) … … 50 45 Task Force (IETF). Note that other groups may also distribute 51 46 working documents as Internet-Drafts. The list of current Internet- 52 53 54 55 Fielding, et al. Expires January 17, 2013 [Page 1]56 57 58 Internet-Draft HTTP/1.1, Part 6 July 201259 60 61 47 Drafts is at http://datatracker.ietf.org/drafts/current/. 62 48 … … 64 50 and may be updated, replaced, or obsoleted by other documents at any 65 51 time. It is inappropriate to use Internet-Drafts as reference 52 53 54 55 Fielding, et al. Expires January 17, 2013 [Page 1] 56 57 58 Internet-Draft HTTP/1.1, Part 6 July 2012 59 60 66 61 material or to cite them other than as "work in progress." 67 62 … … 107 102 3.1. Storing Incomplete Responses . . . . . . . . . . . . . . . 9 108 103 3.2. Storing Responses to Authenticated Requests . . . . . . . 9 109 110 111 112 Fielding, et al. Expires January 17, 2013 [Page 2]113 114 115 Internet-Draft HTTP/1.1, Part 6 July 2012116 117 118 104 4. Constructing Responses from Caches . . . . . . . . . . . . . . 10 119 105 4.1. Freshness Model . . . . . . . . . . . . . . . . . . . . . 11 … … 121 107 4.1.2. Calculating Heuristic Freshness . . . . . . . . . . . 12 122 108 4.1.3. Calculating Age . . . . . . . . . . . . . . . . . . . 13 109 110 111 112 Fielding, et al. Expires January 17, 2013 [Page 2] 113 114 115 Internet-Draft HTTP/1.1, Part 6 July 2012 116 117 123 118 4.1.4. Serving Stale Responses . . . . . . . . . . . . . . . 15 124 119 4.2. Validation Model . . . . . . . . . . . . . . . . . . . . . 16 … … 167 162 168 163 164 165 166 167 168 169 169 Fielding, et al. Expires January 17, 2013 [Page 3] 170 170 -
draft-ietf-httpbis/20/draft-ietf-httpbis-p6-cache-20.xml
r1807 r1809 83 83 <t> 84 84 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 85 distributed, collaborative, hypertext information systems. HTTP has been in 86 use by the World Wide Web global information initiative since 1990. This 87 document is Part 6 of the seven-part specification that defines the protocol 88 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 89 </t> 90 <t> 91 Part 6 defines requirements on HTTP caches and the associated header fields 85 distributed, collaborative, hypertext information systems. This document 86 defines requirements on HTTP caches and the associated header fields 92 87 that control cache behavior or indicate cacheable response messages. 93 88 </t> -
draft-ietf-httpbis/20/draft-ietf-httpbis-p7-auth-20.txt
r1807 r1809 18 18 The Hypertext Transfer Protocol (HTTP) is an application-level 19 19 protocol for distributed, collaborative, hypermedia information 20 systems. HTTP has been in use by the World Wide Web global 21 information initiative since 1990. This document is Part 7 of the 22 seven-part specification that defines the protocol referred to as 23 "HTTP/1.1" and, taken together, obsoletes RFC 2616. 24 25 Part 7 defines the HTTP Authentication framework. 20 systems. This document defines the HTTP Authentication framework. 26 21 27 22 Editorial Note (To be removed by RFC Editor) … … 50 45 Internet-Drafts are draft documents valid for a maximum of six months 51 46 and may be updated, replaced, or obsoleted by other documents at any 52 53 54 55 Fielding, et al. Expires January 17, 2013 [Page 1]56 57 58 Internet-Draft HTTP/1.1, Part 7 July 201259 60 61 47 time. It is inappropriate to use Internet-Drafts as reference 62 48 material or to cite them other than as "work in progress." 63 49 64 50 This Internet-Draft will expire on January 17, 2013. 51 52 53 54 55 Fielding, et al. Expires January 17, 2013 [Page 1] 56 57 58 Internet-Draft HTTP/1.1, Part 7 July 2012 59 65 60 66 61 Copyright Notice … … 90 85 it for publication as an RFC or to translate it into languages other 91 86 than English. 87 88 89 90 91 92 92 93 93 -
draft-ietf-httpbis/20/draft-ietf-httpbis-p7-auth-20.xml
r1807 r1809 74 74 <t> 75 75 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 76 distributed, collaborative, hypermedia information systems. HTTP has been in 77 use by the World Wide Web global information initiative since 1990. This 78 document is Part 7 of the seven-part specification that defines the protocol 79 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 80 </t> 81 <t> 82 Part 7 defines the HTTP Authentication framework. 76 distributed, collaborative, hypermedia information systems. This document 77 defines the HTTP Authentication framework. 83 78 </t> 84 79 </abstract> -
draft-ietf-httpbis/20/p5-range.html
r1807 r1809 495 495 <meta name="dct.issued" scheme="ISO8601" content="2012-07-16"> 496 496 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 497 <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 5defines range requests and the rules for constructing and combining responses to those requests.">498 <meta name="description" 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 5defines range requests and the rules for constructing and combining responses to those requests.">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."> 498 <meta name="description" 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."> 499 499 </head> 500 500 <body onload="init();"> … … 535 535 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 536 536 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 537 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the 538 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 539 </p> 540 <p>Part 5 defines range requests and the rules for constructing and combining responses to those requests.</p> 537 systems. This document defines range requests and the rules for constructing and combining responses to those requests. 538 </p> 541 539 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 542 540 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. -
draft-ietf-httpbis/20/p5-range.xml
r1807 r1809 101 101 <t> 102 102 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 103 distributed, collaborative, hypertext information systems. HTTP has been in 104 use by the World Wide Web global information initiative since 1990. This 105 document is Part 5 of the seven-part specification that defines the protocol 106 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 107 </t> 108 <t> 109 Part 5 defines range requests and the rules for constructing and 110 combining responses to those requests. 103 distributed, collaborative, hypertext information systems. This document 104 defines range requests and the rules for constructing and combining 105 responses to those requests. 111 106 </t> 112 107 </abstract> -
draft-ietf-httpbis/20/p6-cache.html
r1807 r1809 501 501 <meta name="dct.issued" scheme="ISO8601" content="2012-07-16"> 502 502 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 503 <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 6defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">504 <meta name="description" 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 6defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">503 <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."> 504 <meta name="description" 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."> 505 505 </head> 506 506 <body onload="init();"> … … 549 549 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 550 550 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 551 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the 552 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 553 </p> 554 <p>Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable 555 response messages. 551 systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or 552 indicate cacheable response messages. 556 553 </p> 557 554 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> -
draft-ietf-httpbis/20/p6-cache.xml
r1807 r1809 122 122 <t> 123 123 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 124 distributed, collaborative, hypertext information systems. HTTP has been in 125 use by the World Wide Web global information initiative since 1990. This 126 document is Part 6 of the seven-part specification that defines the protocol 127 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 128 </t> 129 <t> 130 Part 6 defines requirements on HTTP caches and the associated header fields 124 distributed, collaborative, hypertext information systems. This document 125 defines requirements on HTTP caches and the associated header fields 131 126 that control cache behavior or indicate cacheable response messages. 132 127 </t> -
draft-ietf-httpbis/20/p7-auth.html
r1807 r1809 492 492 <meta name="dct.issued" scheme="ISO8601" content="2012-07-16"> 493 493 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 494 <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 7defines the HTTP Authentication framework.">495 <meta name="description" 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 7defines the HTTP Authentication framework.">494 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework."> 495 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework."> 496 496 </head> 497 497 <body onload="init();"> … … 533 533 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 534 534 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information 535 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the 536 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 537 </p> 538 <p>Part 7 defines the HTTP Authentication framework.</p> 535 systems. This document defines the HTTP Authentication framework. 536 </p> 539 537 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 540 538 <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. -
draft-ietf-httpbis/20/p7-auth.xml
r1807 r1809 100 100 <t> 101 101 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 102 distributed, collaborative, hypermedia information systems. HTTP has been in 103 use by the World Wide Web global information initiative since 1990. This 104 document is Part 7 of the seven-part specification that defines the protocol 105 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 106 </t> 107 <t> 108 Part 7 defines the HTTP Authentication framework. 102 distributed, collaborative, hypermedia information systems. This document 103 defines the HTTP Authentication framework. 109 104 </t> 110 105 </abstract>
Note: See TracChangeset
for help on using the changeset viewer.