[OT] False timeout error after URL retrieval

[J. Landman Gay]

On May 5, 2015 6:17:48 PM CDT, Trevor DeVore <lists at mangomultimedia.com> wrote:
>On Tuesday, May 5, 2015, Dave Cragg <dave.cragg at lacscentre.co.uk>
>wrote:
>>
>>
>> From memory, I think the size of each chunk is sent with each chunk
>itself
>> in the message portion of the reply, not in the headers.
>
>
> Ah, that would explain it.
>
>libUrl should deal with this. It’s a fairly common transfer method.
>(Sorry,
>> Jacque, I know that doesn’t help you.)
>>
>
>Yes, the code is in there to deal with it.
>
>I have seen similar problem when interacting with wordpress. There are
>plug-ins that mess up the headers for the XML RPC requests. Livecode
>never
>thinks it is done getting data because the content length header is not
>accurate.  Seeing as this problem occurred after an upgrade on the
>server
>the content size information seems like a possible a cause.

I agree. I compared the headers that work with the ones that don't, and the working transmissions do include a content length header. There must be a difference in how the data is being sent. We'll probably do some testing tomorrow. But if libURL handles chunks you'd think those headers would work. Browsers have no trouble with retrieval when we call the URL from there. It's only LiveCode. 

Really appreciate this discussion, the problem has been a difficult one for us. 
-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com