Hi All,
I have made progress with my previous suexec + mod_ldap_user
+ multiple vhosts issue, however I am now getting a strange problem where
suexec is being called when I try accessing a cgi in one vhost but not another:
[pid 23260] read(43, "[EMAIL PROTECTED]
Available\0/u/a/[EMA
According to RFC 2616 section 13.9, if you want the response to a GET
containing a query string (arguments after a ?) to be cached, it MUST contain
an explicit expiration date, i.e. an Expires header. Setting ExpiresDefault
won't make Apache cache such a response no matter what.
I am not sure t
On Mon, 2005-11-28 at 16:15 +, Daniel Berhane wrote:
* Snip *
> authenticate and want mod_rewrite to transfer the URL. The main
> problem, we have is the authentication directives work only under the
> context of "directory" and because the Plone & Zope is a separate
> application ser
It most certainly does work, otherwise I would have been very unhappy.
The bug you refer to concerns doing ProxyPass through a proxy (CONNECT). I did
not see any ProxyRemote in Suzy's configuration.
Here is an example of a virtual host that does use SSLProxyEngine. I currently
use Apache 2.0.54
> [Wed Nov 30 18:34:46 2005] [info] disk_cache: Could not store URL
> 10.209.25.130/images/map/Transport_icon_Train.gif? [13]
I believe the trailing [13] refers to the error returned by a failed system
call. Looking at /usr/include/sys/errno.h tells me that error 13 is EACCES
which translates i
Hi,
I've got the same kind of problem with apache 2.0.49 : lot of processes
remaining in memory.
Databases checked and ok ... Is there a way to tell apache to autokill old
processes ?
Regards,
Fabian
-Message d'origine-
De : Benjamin Adams [mailto:[EMAIL PROTECTED]
Envoyé : v
Hi,
I tried to get Axis to work on XP following the windows installation guide.
I followed the instructions very carefully (and also added an AXIS_HOME
environment variable) but Apache fails to start unless I remove this line:
LoadModule axis_module modules/mod2_axis.dllin the httpd.conf fil
> -Original Message-
> From: Brian C [mailto:[EMAIL PROTECTED]
>
> Reason: DNS lookup failure for: 192.168.0.9dirname
^^
That doesn't look good... Looks like you have missed out a "/" somewhere either
in the config or in a URL on the site
