We are experiencing intermittent connect timeout errors. The remote
service is really ok, but it still results in the worker being
disabled.
Setting the proxypass disable period using retry=1 is not good
enough for the application I'm working with (given the number of
requests we do per
On May 4, 2007, at 11:37 AM, Brian Hayward wrote:
I have 2 questions:
1) What are the negative implications of disabling this?
2) Is there a cleaner way to accomplish this?
So you just want to setup Apache so that even if it
thinks there's an error, to just ignore it?
Hi all,
we are about to extend the Apache Module mod_vhost_ldap.
This module is able to manage vhosts directly from ldap.
Our goal is to completely manage vhost configuration over ldap
including parameters from external modules like mod_dav, php and so
on.
Our plan is to extend this module and
Andreas Kimpfler wrote:
Hi all,
we are about to extend the Apache Module mod_vhost_ldap.
I built my own mod_vhost_ldap extension. Reasoning is at the bottom.
This module is able to manage vhosts directly from ldap.
Our goal is to completely manage vhost configuration over ldap
including
When running an apache that was configured with suexec support as a
random non-root user the variable suexec_enabled is set incorrectly.
The test for availability should really also check access(R_OK|X_OK)
as well as for root ownership and the set uid bit.
This patch fixes the problem and allows
I'm setting up a shared web hosting service running on Linux for
untrusted user content. The standard and supported way of doing this
in Apache is to use mod_userdir and suexec, which causes dynamic
content to be executed using the uid of the mapped user.
However, I don't want to use
On Apr 30, 2007, at 11:15 AM, Joe Schaefer wrote:
Brian McCallister [EMAIL PROTECTED] writes:
+If compiling (make) reports an error that it cannot find the
+libapreq2 header file, please tell me ( [EMAIL PROTECTED] )
+as this occurs under some configurations but we haven't
+
On 5/2/07, Brian McCallister [EMAIL PROTECTED] wrote:
On Apr 30, 2007, at 11:15 AM, Joe Schaefer wrote:
Brian McCallister [EMAIL PROTECTED] writes:
+If compiling (make) reports an error that it cannot find the
+libapreq2 header file, please tell me ( [EMAIL PROTECTED] )
+as
Yea, as it currently stands, one timeout is causing us to lose up to
10 more transactions during the next second (with retry=1)
Thanks,
Brian Hayward
On 5/4/07, Jim Jagielski [EMAIL PROTECTED] wrote:
On May 4, 2007, at 11:37 AM, Brian Hayward wrote:
I have 2 questions:
1) What are the
Well, I doubt completely bypassing setting works to
being in the error state is something you want to do
lightly. :)
PROXY_WORKER_IGNORE_ERRORS is used when setting up
the generic forward and reverse workers, since they
are shared for all requests and not specific
to a balancer/url. I guess
On 04.05.2007 20:16, Brian Hayward wrote:
Yea, as it currently stands, one timeout is causing us to lose up to
10 more transactions during the next second (with retry=1)
With the following patch from trunk you are able to set retry to 0, which
should fix your actual problem:
A few comments intermingled into the patch:
Brian McCallister wrote:
On Apr 30, 2007, at 2:02 PM, Akins, Brian wrote:
--- apr_lua.c (revision 0)
+++ apr_lua.c (revision 0)
@@ -0,0 +1,55 @@
+#include apr.h
+#include apr_tables.h
+
+#include lua.h
+#include lauxlib.h
+#include lualib.h
+
With the following patch from trunk you are able to set retry to 0, which
should fix your actual problem:
Thanks!
But I think in general it is not advisable to do this at least if you are
load balancing your backend / having a failover configuration. And even if
you do not have such a
13 matches
Mail list logo
