[OT] More on false timeouts and headers

[J. Landman Gay]

On 5/22/2015 3:25 AM, Mark Waddingham wrote:
> Thus it seems to me that Dave is correct - this is actually a bug in
> libURL - it is being too lax when parsing headers and interpreting a
> header it should not be thus meaning it is not entering into 'chunked'
> mode even though it is explicitly specified. This is, of course,
> assuming the Content-Transfer-Encoding header appears before the
> Transfer-Encoding header in the full HTTP message body.
>
> So, if indeed the headers being returned from the server are:
>     ...
>     Content-Transfer-Encoding: binary
>     ...
>     Transfer-Encoding: chunked
>
> Then libUrl should be ignoring the CTE header, and carrying on its merry
> way - in this context Dave's patch to libURL should solve the issue for
> you.

That's exactly how the headers are arranged. Content-Transfer-Encoding: 
binary appears before Transfer-Encoding: chunked.

I'll implement Dave's fix in my copy of libURL. This has been very 
informative. Will you update the shipping version of libURL without me, 
or should I post a bug report?

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com