minf...@apache.org wrote:
Author: minfrin
Date: Tue May 7 20:27:37 2013
New Revision: 1480058
URL: http://svn.apache.org/r1480058
Log:
mod_proxy: Ensure network errors detected by the proxy are returned as
504 Gateway Timout as opposed to 502 Bad Gateway, in order to be
compliant with
On 08 May 2013, at 9:47 AM, Ruediger Pluem rpl...@apache.org wrote:
I don't agree with this. The case you mention is only true if the client
sends Cache-Control: must-revalidate.
If this is not the case IMHO 10.5.3 and 10.5.5 apply.
And only a cache is required to respond with 504 in this
Graham Leggett wrote:
On 08 May 2013, at 9:47 AM, Ruediger Pluem rpl...@apache.org wrote:
I don't agree with this. The case you mention is only true if the client
sends Cache-Control: must-revalidate.
If this is not the case IMHO 10.5.3 and 10.5.5 apply.
And only a cache is required to
I think you need to screen out 4xx at least to prevent client errors
from marking down your backends.
Seems like those responses never reach that code. Neither 400 nor 401 or
403 had an effect on the worker's error state, it always remained in state
'OK'. I'd like to say it's not an issue but
On 05/03/2013 05:28 PM, David Mansfield wrote:
I'm hitting this bug (I think):
https://issues.apache.org/bugzilla/show_bug.cgi?id=53692
This bug makes the mode described in the docs. for mod_auth_form
called Inline with Body Preservation impossible, because it's
impossible to access the
On Mon, 6 May 2013 23:42:27 +0100
Tom Jones t...@inpher.com wrote:
We use process supervision and don't have a use for pid files. We
are running multiple httpd instances, and have the config management
to create a writable configured place for each instance to put its
pid file.
Surely you
On 08.05.2013 20:06, William A. Rowe Jr. wrote:
On Mon, 6 May 2013 23:42:27 +0100
Tom Jones t...@inpher.com wrote:
We use process supervision and don't have a use for pid files. We
are running multiple httpd instances, and have the config management
to create a writable configured place
On May 8, 2013, at 1:11 AM, Ruediger Pluem wrote:
Graham Leggett wrote:
On 08 May 2013, at 9:47 AM, Ruediger Pluem rpl...@apache.org wrote:
I don't agree with this. The case you mention is only true if the client
sends Cache-Control: must-revalidate.
If this is not the case IMHO 10.5.3 and
On 5/8/2013 3:29 PM, Rainer Jung wrote:
Careful: I didn't test it but we delete the pid file during web server
shutdown. That might remove /dev/null then.
On a quick look through the code I had the impression you can not easily
get rid of the pid file.
Agreed - setting to /dev/null under the
