Le 06/02/2014 10:53, Christian Weiske a écrit :
Hello Klaas,
[Fri Jan 31 11:02:06 2014] [warn] [client 91.66.218.142]
mod_fcgid: read data timeout in 40 seconds
[Fri Jan 31 11:02:06 2014] [error] [client 91.66.218.142]
He is using FCGI (FastCGI), which starts separate PHP processes and
waits for a couple of seconds. If the PHP process doesn't respond
within that time, cgi will see it as "fail" and send a 500 back to
the client.
The PHP process will still run on.
Ok, in that cas e there is no chance at all to handle that correctly.
Oh, there is.
The server app could send a dot or whatever every couple of seconds, so
that there is something to send to the client and the cgi process sees
that the php process did not crash.
Or finish early with a "processing" state, put it in a queue and let the
client pull every couple of seconds to see if it's done.
Hello,
That would be great and necessary because nowadays, FastCGI/PHP-FPM
mechanisms are largely used to perform better.
_______________________________________________
Owncloud mailing list
Owncloud@kde.org
https://mail.kde.org/mailman/listinfo/owncloud
_______________________________________________
Owncloud mailing list
Owncloud@kde.org
https://mail.kde.org/mailman/listinfo/owncloud
