On Mon, Jul 10, 2017 at 3:31 PM, Mark Thomas <ma...@apache.org> wrote:
> On 10/07/17 20:59, Mark Thomas wrote: > > On 08/07/17 20:06, Mark Thomas wrote: > >> On 07/07/17 23:05, George Stanchev wrote: > > > > <snip/> > > > >>> Since you cannot reproduce it, perhaps I can package up the tomcat + > the > > test app in a zip and upload it somewhere... > >> > >> That would be helpful. I've tested this in multiple environments and I > >> can't reproduce it. > > > > Many thanks to George for putting together the test case. I have now > > been able to reproduce this. > > > > The problem is related to the new code that handles the case when a file > > is stored in one encoding but served in another. Since changing > > encodings can change the value and number of bytes served (for example > > serving £ in UTF-8 requires two bytes but only one in ISO-8859-1). This > > code did not handle requests that use accept-ranges correctly. > > While the above is true, the actual problem looking more closely is that > the content length can change when conversion is used. > > Yes, so I think your fix is right: it's not possible to do a range request in that case. Rémy
