On Nov 29, 2008, at 02:34, David Woolley wrote:
Dries.DeMoor wrote:
The call to the url starts some processing which takes more than 5
hours.
Most browsers would give up after just a few minutes!
I believe there is an HTTP response (Status 100???) which allows
one to say "please wait".
[EMAIL PROTECTED] wrote:
The call to the url starts some processing which takes more than 5 hours.
Most browsers would give up after just a few minutes!
I believe there is an HTTP response (Status 100???) which allows one to
say "please wait". If that's right and Lynx supports it, a better
On Wed, 26 Nov 2008, [EMAIL PROTECTED] wrote:
We're using lynx in a job that's scheduled every night. In the job lynx
makes a call to a certain web-url.
The problem we have is that linx give the following message:
HTTP request sent; waiting for response.
Alert!: Socket read failed for 180,00
Dear,
We're using lynx in a job that's scheduled every night. In the job lynx
makes a call to a certain web-url.
The problem we have is that linx give the following message:
HTTP request sent; waiting for response.
Alert!: Socket read failed for 180,000 tries.
Connection interrupted.
