Re: Range Requests vs Content Codings

On 2014-06-18 07:52, Mark Nottingham wrote:
>
> On 18 Jun 2014, at 3:29 pm, Julian Reschke <julian.reschke@gmx.de> wrote:
>
>>> Also, this won't work with intermediaries until they actually support it.
>>
>> Um, no. Intermediaries can ignore it. It just makes all responses using the new range unit uncacheable.
>>
>> Intermediaries that fail for unknown range units are broken, no?
>
> Yes, of course they wouldn't break, but they also wouldn't be able to cache partial responses using the new range-unit, nor would they be able to
> service requests that use it. So there's a loss of functionality which may outweigh the usefulness of the new function.

That is true. It would effectively be end-to-end with no benefits of 
intermediary caching.

> ...

Best regards, Julian

Received on Wednesday, 18 June 2014 06:01:07 UTC