From: Matthew Kerwin Date: 2016-02-17T08:04:31+10:00 Subject: [ruby-core:73856] Re: [Ruby trunk Bug#12055] `NET::HTTPResponse` is not deflating responses with custom `Content-Range` header --===============1831740180== Content-Type: multipart/alternative; boundary=001a11c301dc6d5e2d052bea515c --001a11c301dc6d5e2d052bea515c Content-Type: text/plain; charset=UTF-8 On 17/02/2016 1:40 AM, wrote: > > Issue #12055 has been updated by Glauber Campinho. > > > ping > This should be rejected. Content Encoding is applied by the server *before* Range; and therefore must be applied by the client *after* Range. (This is true for all range units, not just bytes.) So you can't automatically inflate *any* partial response. The current implementation looks correct. --001a11c301dc6d5e2d052bea515c Content-Type: text/html; charset=UTF-8


On 17/02/2016 1:40 AM, <ggcampinho@gmail.com> wrote:
>
> Issue #12055 has been updated by Glauber Campinho.
>
>
> ping
>

This should be rejected.

Content Encoding is applied by the server *before* Range; and therefore must be applied by the client *after* Range. (This is true for all range units, not just bytes.)

So you can't automatically inflate *any* partial response.

The current implementation looks correct.

--001a11c301dc6d5e2d052bea515c-- --===============1831740180== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Unsubscribe: --===============1831740180==--