https://issues.apache.org/bugzilla/show_bug.cgi?id=51714
--- Comment #2 from Mikko Parviainen <[email protected]> 2011-08-26 10:13:11 UTC --- First, I'm not an expert on the matter. A small addition might be in place to the work-around option suggested in: <http://marc.info/?l=apache-httpd-dev&m=131418828705324&w=2> The first mitigation option was a configuration change: RequestHeader unset Range In addition to dropping the "Range" from request headers, it might prove useful to drop the "If-Range" as well, and might also be polite to respond with "Accept-Ranges: none". This could be accomplished with: # Removes the "Range" and "If-Range" from the request headers RequestHeader unset Range RequestHeader unset If-Range # Removes all "Accept-Ranges" from the response headers Header unset Accept-Ranges # Sets "Accept-Ranges: none" to the response headers Header set Accept-Ranges none (I'm not sure if the "Header unset Accept-Ranges" is even necessary.) According to the HTTP 1.1 specification RFC 2616: * "Servers that do not accept any kind of range request for a resource MAY send 'Accept-Ranges: none'" (section 14.5); and * "A server MAY ignore the Range header" (section 14.35.2). But clearly this is only a work-around. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
