`NET::HTTPResponse` is not deflating responses with custom `Content-Range` header
The RFC 7233, section 4.2 describes the the possibility of using a custom
Content-Range header and not only for bytes https://tools.ietf.org/html/rfc7233#section-4.2. Although, the
NET::HTTPResponse considers that
Content-Range present on the response during the inflating is in
This issue is caused by this line https://github.com/ruby/ruby/blob/trunk/lib/net/http/response.rb#L252. In the patch I changed it to check if the
Content-Range unit is
bytes and there is a test to reproduce the error.
Updated by Anonymous 4 months ago
- Status changed from Assigned to Closed
Applied in changeset git|63546bfc1581d4abec2a0d846106a1c0afc0efa9.
HTTPHeader.content_range throws error on non-byte units
- Added a nil check in Net::HTTPHeader#initialize_http_header for keys in the header that do not have any value
- Returning nil from the content_range method instead of raising an error when the unit in the content-range header is not bytes
- Modified initialize_http_header to match trunk