Changeset 1740 for draft-ietf-httpbis/latest/p5-range.xml
- Timestamp:
- 08/07/12 18:15:03 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.xml
r1739 r1740 187 187 impact on security. This is because different uses of the protocol require 188 188 different error handling strategies; for example, a Web browser might wish to 189 transparently recover from a response where the Location header field 190 doesn't parse according to the ABNF, whereby in a systems control protocol 191 using HTTP, this type of error recovery could lead to dangerous consequences. 189 transparently recover from a response where the <x:ref>Location</x:ref> 190 header field doesn't parse according to the ABNF, whereby in a systems 191 control protocol using HTTP, this type of error recovery could lead to 192 dangerous consequences. 192 193 </t> 193 194 </section> … … 329 330 (<xref target="header.content-range"/>) indicating 330 331 the range included with this response, or a multipart/byteranges 331 Content-Type including Content-Range fields for each part. If a332 Content-Length header field is present in the response, its333 value &MUST; match the actual number of octets transmitted in the334 message body.332 <x:ref>Content-Type</x:ref> including Content-Range fields for each 333 part. If a <x:ref>Content-Length</x:ref> header field is present in the 334 response, its value &MUST; match the actual number of octets 335 transmitted in the message body. 335 336 </t> 336 337 <t> … … 339 340 <t> 340 341 <x:ref>Cache-Control</x:ref>, <x:ref>ETag</x:ref>, 341 <x:ref>Expires</x:ref>, Content-Locationand/or342 <x:ref>Expires</x:ref>, <x:ref>Content-Location</x:ref> and/or 342 343 <x:ref>Vary</x:ref>, if the header field would have been sent in a 343 344 <x:ref>200 (OK)</x:ref> response to the same request … … 1008 1009 </front> 1009 1010 <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/> 1010 <x:source href="p1-messaging.xml" basename="p1-messaging"/> 1011 <x:source href="p1-messaging.xml" basename="p1-messaging"> 1012 <x:defines>Content-Length</x:defines> 1013 </x:source> 1011 1014 </reference> 1012 1015 … … 1032 1035 <x:defines>200 (OK)</x:defines> 1033 1036 <x:defines>410 (Gone)</x:defines> 1037 <x:defines>Content-Location</x:defines> 1038 <x:defines>Content-Type</x:defines> 1039 <x:defines>Location</x:defines> 1034 1040 </x:source> 1035 1041 </reference> … … 1260 1266 <t> 1261 1267 The multipart/byteranges media type includes one or more parts, each 1262 with its own Content-Type and <x:ref>Content-Range</x:ref> fields. The1263 required boundary parameter specifies the boundary string used to separate1264 each body-part.1268 with its own <x:ref>Content-Type</x:ref> and <x:ref>Content-Range</x:ref> 1269 fields. The required boundary parameter specifies the boundary string used 1270 to separate each body-part. 1265 1271 </t> 1266 1272 <t>
Note: See TracChangeset
for help on using the changeset viewer.