Changeset 1055 for draft-ietf-httpbis/12
- Timestamp:
- 23/10/10 09:17:48 (12 years ago)
- Location:
- draft-ietf-httpbis/12
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/12/draft-ietf-httpbis-p1-messaging-12.txt
r1051 r1055 2015 2015 described in Section 9.5; or, 2016 2016 2017 2. the server is the origin server for the response, the trailer2018 fields consist entirely of optional metadata, and the recipient2019 could use the message (in a manner acceptable to the origin2020 server) without receiving this metadata. In other words, the2021 origin server is willing to accept the possibility that the2022 t railer fields might be silently discarded along the path tothe2023 client.2017 2. the trailer fields consist entirely of optional metadata, and the 2018 recipient could use the message (in a manner acceptable to the 2019 server where the field originated) without receiving it. In 2020 other words, the server that generated the header (often but not 2021 always the origin server) is willing to accept the possibility 2022 that the trailer fields might be silently discarded along the 2023 path to the client. 2024 2024 2025 2025 This requirement prevents an interoperability failure when the … … 4856 4856 Closed issues: 4857 4857 4858 o <http://tools.ietf.org/wg/httpbis/trac/ticket/193>: "Trailer 4859 requirements" 4860 4858 4861 o <http://tools.ietf.org/wg/httpbis/trac/ticket/204>: "Text about 4859 4862 clock requirement for caches belongs in p6" … … 4892 4895 gzip 38 4893 4896 compress (Coding Format) 38 4897 4898 4899 4900 Fielding, et al. Expires April 28, 2011 [Page 86] 4901 4902 4903 Internet-Draft HTTP/1.1, Part 1 October 2010 4904 4905 4894 4906 connection 10 4895 4907 Connection header 49 4896 4908 Content-Length header 50 4897 4898 4899 4900 Fielding, et al. Expires April 28, 2011 [Page 86]4901 4902 4903 Internet-Draft HTTP/1.1, Part 1 October 20104904 4905 4909 4906 4910 D … … 4948 4952 DIGIT 7 4949 4953 DQUOTE 7 4954 4955 4956 4957 Fielding, et al. Expires April 28, 2011 [Page 87] 4958 4959 4960 Internet-Draft HTTP/1.1, Part 1 October 2010 4961 4962 4950 4963 extension-code 32 4951 4964 extension-method 26 4952 4965 field-content 20 4953 4966 field-name 20 4954 4955 4956 4957 Fielding, et al. Expires April 28, 2011 [Page 87]4958 4959 4960 Internet-Draft HTTP/1.1, Part 1 October 20104961 4962 4963 4967 field-value 20 4964 4968 general-header 26 … … 5005 5009 Request 26 5006 5010 Request-Line 26 5011 5012 5013 5014 Fielding, et al. Expires April 28, 2011 [Page 88] 5015 5016 5017 Internet-Draft HTTP/1.1, Part 1 October 2010 5018 5019 5007 5020 request-target 27 5008 5021 Response 31 5009 5022 rfc850-date 34 5010 5023 rfc1123-date 33 5011 5012 5013 5014 Fielding, et al. Expires April 28, 2011 [Page 88]5015 5016 5017 Internet-Draft HTTP/1.1, Part 1 October 20105018 5019 5020 5024 RWS 9 5021 5025 second 33 … … 5062 5066 Host 52 5063 5067 TE 53 5068 5069 5070 5071 Fielding, et al. Expires April 28, 2011 [Page 89] 5072 5073 5074 Internet-Draft HTTP/1.1, Part 1 October 2010 5075 5076 5064 5077 Trailer 54 5065 5078 Transfer-Encoding 55 5066 5079 Upgrade 55 5067 5080 Via 57 5068 5069 5070 5071 Fielding, et al. Expires April 28, 2011 [Page 89]5072 5073 5074 Internet-Draft HTTP/1.1, Part 1 October 20105075 5076 5077 5081 headers 19 5078 5082 Host header 52 … … 5119 5123 Upgrade header 55 5120 5124 upstream 12 5125 5126 5127 5128 Fielding, et al. Expires April 28, 2011 [Page 90] 5129 5130 5131 Internet-Draft HTTP/1.1, Part 1 October 2010 5132 5133 5121 5134 URI scheme 5122 5135 http 16 5123 5136 https 18 5124 5137 user agent 10 5125 5126 5127 5128 Fielding, et al. Expires April 28, 2011 [Page 90]5129 5130 5131 Internet-Draft HTTP/1.1, Part 1 October 20105132 5133 5138 5134 5139 V … … 5169 5174 5170 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 Fielding, et al. Expires April 28, 2011 [Page 91] 5186 5187 5188 Internet-Draft HTTP/1.1, Part 1 October 2010 5189 5190 5171 5191 Henrik Frystyk Nielsen 5172 5192 Microsoft Corporation … … 5176 5196 5177 5197 EMail: henrikn@microsoft.com 5178 5179 5180 5181 5182 5183 5184 5185 Fielding, et al. Expires April 28, 2011 [Page 91]5186 5187 5188 Internet-Draft HTTP/1.1, Part 1 October 20105189 5198 5190 5199 … … 5219 5228 5220 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 Fielding, et al. Expires April 28, 2011 [Page 92] 5243 5244 5245 Internet-Draft HTTP/1.1, Part 1 October 2010 5246 5247 5221 5248 Yves Lafon (editor) 5222 5249 World Wide Web Consortium … … 5230 5257 5231 5258 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 Fielding, et al. Expires April 28, 2011 [Page 92]5243 5244 5245 Internet-Draft HTTP/1.1, Part 1 October 20105246 5247 5248 5259 Julian F. Reschke (editor) 5249 5260 greenbytes GmbH … … 5286 5297 5287 5298 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5299 Fielding, et al. Expires April 28, 2011 [Page 93] 5300 5300 -
draft-ietf-httpbis/12/draft-ietf-httpbis-p1-messaging-12.xml
r1051 r1055 2047 2047 acceptable in the transfer-coding of the response, as described in 2048 2048 <xref target="header.te"/>; or,</t> 2049 2050 <t>the server is the origin server for the response, the trailer2051 fields consist entirely of optional metadata, and the recipient2052 could use the message (in a manner acceptable to the origin server)2053 without receiving this metadata. In other words, the origin server2054 is willing to accept the possibility that the trailer fields might2055 be silently discardedalong the path to the client.</t>2049 2050 <t>the trailer fields consist entirely of optional metadata, and the 2051 recipient could use the message (in a manner acceptable to the server where 2052 the field originated) without receiving it. In other words, the server that 2053 generated the header (often but not always the origin server) is willing to 2054 accept the possibility that the trailer fields might be silently discarded 2055 along the path to the client.</t> 2056 2056 </list> 2057 2057 </t> … … 5612 5612 <list style="symbols"> 5613 5613 <t> 5614 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/193"/>: 5615 "Trailer requirements" 5616 </t> 5617 <t> 5614 5618 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/204"/>: 5615 5619 "Text about clock requirement for caches belongs in p6" -
draft-ietf-httpbis/12/p1-messaging.html
r1051 r1055 1634 1634 described in <a href="#header.te" id="rfc.xref.header.te.2" title="TE">Section 9.5</a>; or, 1635 1635 </li> 1636 <li>the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the recipient 1637 could use the message (in a manner acceptable to the origin server) without receiving this metadata. In other words, the origin 1638 server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client. 1636 <li>the trailer fields consist entirely of optional metadata, and the recipient could use the message (in a manner acceptable 1637 to the server where the field originated) without receiving it. In other words, the server that generated the header (often 1638 but not always the origin server) is willing to accept the possibility that the trailer fields might be silently discarded 1639 along the path to the client. 1639 1640 </li> 1640 1641 </ol> … … 3455 3456 <p id="rfc.section.D.13.p.1">Closed issues: </p> 3456 3457 <ul> 3458 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/193">http://tools.ietf.org/wg/httpbis/trac/ticket/193</a>>: "Trailer requirements" 3459 </li> 3457 3460 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/204">http://tools.ietf.org/wg/httpbis/trac/ticket/204</a>>: "Text about clock requirement for caches belongs in p6" 3458 3461 </li> -
draft-ietf-httpbis/12/p1-messaging.xml
r1051 r1055 2086 2086 acceptable in the transfer-coding of the response, as described in 2087 2087 <xref target="header.te"/>; or,</t> 2088 2089 <t>the server is the origin server for the response, the trailer2090 fields consist entirely of optional metadata, and the recipient2091 could use the message (in a manner acceptable to the origin server)2092 without receiving this metadata. In other words, the origin server2093 is willing to accept the possibility that the trailer fields might2094 be silently discardedalong the path to the client.</t>2088 2089 <t>the trailer fields consist entirely of optional metadata, and the 2090 recipient could use the message (in a manner acceptable to the server where 2091 the field originated) without receiving it. In other words, the server that 2092 generated the header (often but not always the origin server) is willing to 2093 accept the possibility that the trailer fields might be silently discarded 2094 along the path to the client.</t> 2095 2095 </list> 2096 2096 </t> … … 5657 5657 <list style="symbols"> 5658 5658 <t> 5659 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/193"/>: 5660 "Trailer requirements" 5661 </t> 5662 <t> 5659 5663 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/204"/>: 5660 5664 "Text about clock requirement for caches belongs in p6"
Note: See TracChangeset
for help on using the changeset viewer.