Hi Ray
There is an outstanding bug report about cases where socket closing
doesn't seem to be handled properly.
http://quality.runrev.com/qacenter/show_bug.cgi?id=2955
I don't know if this is the same. But you could try adding a
"Connection: close" http header.
set the httpHeaders to "Connection: close"
Or if you already have httpHeaders set:
set the httpHeaders to the httpHeaders & cr & "Connection: close"
Dave
On 20 Oct 2009, at 23:53, Ray Horsley wrote:
Some of our users are intermittently getting this error "error
socket is not open" in the result when posting an http request to a
web server. I'm unable to repeat it. The standalone is not in the
startup process and I'm sure the internet library was included in
the build. Any ideas on why or how to test for this?
Thanks,
Ray Horsley
LinkIt! Software
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
