I understand it's not always possible to respond to a range request - if
you're generating a response on the fly, you might not know how long
your response will be so you could send back unsatisfiable or unknown at
this time if anyone tries that on a dynamic request.

Rather than nail this properly, someone found time to define 418 I'm a
teapot (RFC 2324 <https://tools.ietf.org/html/rfc2324>)

Sigh :)

Ah well, like you say, is what it is & can always hack http servers to
my liking if it proves to be a problem.

Fairly low on the list right now.

Thanks, Daniel.

Best regards,
Steve.

On 31/07/17 23:31, Daniel Stenberg wrote:
> On Mon, 31 Jul 2017, Steve Williams wrote:
>
>> Thanks Ray. I got something working that will do for now but not a
>> fan of the non-deterministic nature of range request responses.
>>
>> Realize this is an http standards committee issue rather than
>> anything curl specific. curl handles the protocol as best it can.
>
> HTTP ranges were defined that way from the start. For example, sites
> that generate their responses on the fly could have a really hard time
> to support byte ranges, so the protocol doesn't mandate servers to
> support it.
>
> A bit unfortunate, sure, but now a fact of life...
>

-- 
Best regards,
Steve Williams
Managing Director
Advance Software Limited
Mobile: +44 (0)745 9344854
Skype: steve--w
<><> Infinity is here...
Get your free 3D web browser today : http://advance-software.com/products
How does your organisation plan to exploit the virtual reality opportunity ?
Visit our 3D web portal : http://infinity-online.net
https://www.facebook.com/advance.sw
Twitter : @AdvanceSoftware
https://www.linkedin.com/in/advsw

-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2017-08-01