codesite-noreply at google
Nov 25, 2009, 1:14 AM
Post #10 of 40
Comment #27 on issue 504 by alobbs: 504 Gateway error
Re: Issue 504 in cherokee: 504 Gateway error
[In reply to]
@jjamor: A few days ago, I committed a few patches for adding custom
to rule entries. That means, a specific rule can define a timeout value,
as it can
define a encoding method, o a handler plug-in.
The target was to allow PHP connections to last longer and the general
so the server wouldn't reply a 504 error if the php-cgi was still (hanged)
the request when the timeout limit was reached.
I've just realized that, you might be hitting that issue in the back-end
Depending on the wiki software processing speed, the back-end web server
returning 504 errors whenever that process takes longer than the general
limit. In that case, the front-end proxy server would be just relying it to
I have not probed that theory yet, but it makes good sense to me.
The best way to test it would be to add a custom timeout to the Extension
PHP rule of
the back-end servers. A 35 seconds value would be enough (since php.ini
seconds of processing limit by default). Hopefully that will fix the issue.
Cherokee 0.99.30 will ship an improved version of the PHP wizard. It checks
php.ini file in order to figure the right timeout value. In that way it can
right timeout value to the rule, so it does not return 504 errors when php
takes a "long" time to be executed (longer than the server-wide timeout
BTW, I'm talking about PHP, but the underlying idea applies to any other
language as well.
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
Cherokee-dev mailing list
Cherokee-dev [at] lists