On 24 Apr 2011, at 18:19, David Beck wrote:
> If I send a "Connection: close" with the httpHeaders, everything works as
> expected with no hang. In this case, by using using the logging feature in
> libURL, I could see that the response header have "connection: close" instead
> of "connection:
runrev.com wrote:
Message: 6
Date: Fri, 22 Apr 2011 20:15:52 +0100
From: Dave Cragg
To: How to use LiveCode
Subject: Re: libURL hangs after getting response with keep-alive
header
Message-ID:<7cdf3b9d-eef9-4a6e-bbb5-0f77eb14c...@lacscentre.co.uk>
Content-Type: text/plain; charset=us
FYI: Not sure if this relates:
I recently set Keep Alive on (300 connections) in the core httpd.conf
on our web server... (recommended for performance)
and I'm not having any difficulty with any of my desktop stacks or
handlers that talk to our server (I have a dozen or these, 2 or 3 of
w
David
As an after thought..
Does it help if you set the httpHeaders to "Connection: close"?
Dave
On 22 Apr 2011, at 20:00, David Beck wrote:
>
> Before I report this as a bug, maybe somebody can shine some light on what is
> going on here.
>
> It looks like libURL hangs after getting a res
David
Unless something has changed in the recent versions of libUrl (and I can't find
anything obvious), libUrl will ignore any "Connection: keep-alive" header in
the response.
By default, it will keep connections open unless there was a "Connection:
close" header in the response.
Could there
