[bug #60106] wget mistakenly interprets Content-Range as bytes, even with Range-Unit: items, and truncates content

[Darshit Shah]

Update of bug #60106 (project wget):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #2:

Hi,

As far as I can tell, the "Range-Unit" header is not mentioned in any of the
HTTP/1.1 Specifications (RFC 7230-7237). The correct way to specify the range
unit would be to add the unit in the "content-range" header itself. This is
very clearly outlined in both RFC2616, the original HTTP/1.1 specification and
in RFC7233 the latest version of HTTP/1.1. Please refer to the ABNF provided
there to create valid HTTP responses that comform to the specification.

By the specification, if the unit is not specified, the client is allowed to
interpret it as Bytes, which is exactly what Wget does.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60106>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/