libURL hangs after getting response with keep-alive header

[Dave Cragg]

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 be something else going on that is causing the problem?



Cheers
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
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode