DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27715>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27715 Client sending misformed Range "bytes = 0-100" instead "bytes=0-100" [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Component|core |Core Keywords| |PatchAvailable Product|Apache httpd-1.3 |Apache httpd-2.0 Summary|Apache dosn't understand |Client sending misformed |"Range:" header if client |Range "bytes = 0-100" |sent "bytes = 0-100" instead|instead "bytes=0-100" |"bytes=0-100" | Version|1.3.29 |2.0-HEAD ------- Additional Comments From [EMAIL PROTECTED] 2004-03-16 18:02 ------- In 14.35.1 of RFC2616 I'm not seeing it... ranges-specifier = byte-ranges-specifier byte-ranges-specifier = bytes-unit "=" byte-range-set byte-range-set = 1#( byte-range-spec | suffix-byte-range-spec ) byte-range-spec = first-byte-pos "-" [last-byte-pos] first-byte-pos = 1*DIGIT last-byte-pos = 1*DIGIT But in the be liberal in what you parse, strict in what you send, I'd accept LWS parsing within Range tags. Other comments? I've reclassed as a 2.0 bug to draw attention and interest :) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
