Changeset 1685 for draft-ietf-httpbis/latest/p5-range.xml
- Timestamp:
- 22/06/12 07:32:37 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.xml
r1684 r1685 115 115 <note title="Editorial Note (To be removed by RFC Editor)"> 116 116 <t> 117 Discussion of this draft shouldtake place on the HTTPBIS working group117 Discussion of this draft ought to take place on the HTTPBIS working group 118 118 mailing list (ietf-http-wg@w3.org), which is archived at 119 119 <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>. … … 623 623 <t> 624 624 If the server ignores a byte-range-spec (for example if it is 625 syntactically invalid, or if it m aybe seen as a denial-of-service625 syntactically invalid, or if it might be seen as a denial-of-service 626 626 attack), the server &SHOULD; treat the request as if the invalid Range 627 627 header field did not exist. (Normally, this means return a 200 … … 963 963 <section title="Overlapping Ranges" anchor="overlapping.ranges"> 964 964 <t> 965 Range requests containing overlapping ranges maylead to the situation965 Range requests containing overlapping ranges can lead to the situation 966 966 where a server is sending far more data than the size of the complete 967 967 resource representation.
Note: See TracChangeset
for help on using the changeset viewer.