Bug 49825

reference: http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/dav/main/mod_dav.c?revision= 982016&view=markup

In dav_parse_range(), called by dav_method_put(), a failure to parse the Content-Range request-header is treated the same as if the header were absent. I think this is wrong for several reasons:

1, Apache's current behavior is pretty much guaranteed to not be the behavior the client needs or expects; if I'm attempting to patch the middle of a file, I don't want the server to replace the entire file with the patch and then report success.

2, although comments in mod_dav.c indicate that the behavior is motivated by RFC2616 [14.16], the relevant paragraph says: "The recipient of an invalid byte-content-range-spec MUST ignore it and any content transferred along with it." In other words, the server is required *not to use* the request entity-body if it is accompanied by an unparsable Content-Range header.

I think that both RFC2616 and common sense indicate that if dav_parse_range() cannot parse a Content-Range header, Apache should reject the entire request (presumably with an HTTP 400 error code).