[solved] Retry with new instance.

[IanD]

No, that's just to do with retrying automatic proxy configuration.

Is 408 the most appropriate status to be sent here?

408 Request Timeout
The server timed out waiting for the request.[2] According to W3 HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time."

That isn't strictly true (in my circumstances anyway), the client DID produce a valid request but the server was just too busy to respond in the required time.

I would have thought this should be a 503 - to which I would presume Firefox wouldn't automatically refresh the URL.

[mistwang]

Please download 4.0.20 again, changed the code to 500.

[IanD]

It works!

Firefox displays the 500 Request Timeout page and doesn't try to refresh it.

Thanks guys - you do an awesome job here. Really listening to your customers, it's great.

[adnet]

Originally Posted by NiteWave

we just added new feature on 4.0.19 to address this timeout issue:
"added another special rewrite environment variable "noconntimeout", this will disable connection timeout, it will keep the connection open forever till the request complete."

for example:

RewriteRule abc.php - [E=noconntimeout:1]

please test at your end, see if it 100% resolves your issue.

Is it in the admin ?

[webizen]

It is environment variable in rewrite rule.

you can add that rule 'RewriteRule ... [E=noconntimeout:1]' in .htaccess or in Rewrite box for LSWS native vhost.