A while back I realized the futility of using a single httpd.conf after having
many errors due to not repeating things correctly in SSL section and the long
length of the file.
I broke it up into a httpd.conf, mod_gzip.conf, a global SSL.conf and a conf
file (and SSL version if needed) for each
On 9/27/2010 6:09 AM, Peter Janovsky wrote:
> Are you returning the value of 200 within a module you've written? I
> encountered a
> similar issue within a C module specific to valid requests. It was resolved
> by returning
> the internal constant OK.
This is a generalized issue of serving Err
Cédric,
Je schreef:
Hello,
I apologize for such a trivial question, but I'd like to use a
function other than "handler" as a perl handler. According to the doc,
it was possible in mod_perl 1, but I can't manage to get it to work
under mod_perl 2.
I am using Apache2::RequestRec which fine
Greetings,
We have a problem with huge Apache+mod_perl2 processes of 150-200 Mb in size.
After apache restart they are usually 40-50 Mb in size, then in a minute grow
up to 100-150 Mb and then some time later may grow up to 200 Mb. I suspect a
certain type of http queries and would like to know
We use a combination of Perl sections and Template Toolkit to generate our
apache configs. The Perl sections are good for run-time setup for things like
host names (i.e., to name logs per host in our cluster) and the templating is
good for setting up things like multiple proxies that have just
On 10/01/2010 04:47 PM, Chris Bennett wrote:
At this point, should I break the AuthCookie sections out into confs for
each virtual host using it, learn to use Perl Sections, or something
different? Any suggestions are welcome.
We actually like using templated httpd.conf files (we use
HTML::Te
A while back I realized the futility of using a single httpd.conf after
having many errors due to not repeating things correctly in SSL section
and the long length of the file.
I broke it up into a httpd.conf, mod_gzip.conf, a global SSL.conf and a
conf file (and SSL version if needed) for each
On 30 Sep 2010, at 19:58, Fred Moyer wrote:
> To simplify the Apache::Test codebase, the custom configuration
> feature is being considered for removal. Is anyone here using that
> feature? If you don't know what it is, you aren't using it.
I don't believe we do, but could you give us a quick
On Thursday, September 30, 2010 20:58:28 Fred Moyer wrote:
> To simplify the Apache::Test codebase, the custom configuration
> feature is being considered for removal. Is anyone here using that
> feature? If you don't know what it is, you aren't using it.
For those of us who are a bit at a loss
