Hi Dave,
Thanks for you help.
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: keep-alive".
It looks like there are several places were libURL tests for the
"Connection: close" header in the response, but I don't see it testing
for a "keep-alive" header anywhere.
Should I log this as a bug?
Thanks!
David
[email protected] wrote:
Message: 6
Date: Fri, 22 Apr 2011 20:15:52 +0100
From: Dave Cragg<[email protected]>
To: How to use LiveCode<[email protected]>
Subject: Re: libURL hangs after getting response with keep-alive
header
Message-ID:<[email protected]>
Content-Type: text/plain; charset=us-ascii
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 response with a "Connection: keep-alive" in it. It pretty much freeze up the entire IDE, except for the message box, which you can use to unfreeze everything in most cases by issuing the "resetall" command.
>
> Shouldn't it just treat it as a "Connection: close" header, if it does not support keeping connections alive?
>
> Also, it sounds like in HTTP1.1, the default is that all connections are kept alive, unless a "Connection: close" header is sent with the request. Therefore, shouldn't libURL be sending that "Connection: close" header, since it doesn't support keep-alive?
>
> Thanks in advance,
>
> David Beck
>
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
