Apache 2.0.46, W2K, working on a module...
I'm tracing calls to the module's dir/svr create/merge calls (the ones
specified in the module data object along with a pointer to the command
array and the hook register function). I'm not clear on when Apache should
be calling the merge functions.
If
Sorry...I intended to put this on 'modules'...which I have now done...mea
culpa
-Original Message-
From: Marc M. Adkins [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2003 12:21 PM
To: [EMAIL PROTECTED]
Subject: merge_dir_config calls
Is adding 'blocks' (e.g. Perl.../Perl) in configuration files encouraged
or discouraged? I've been considering one such in a module of mine, and
looking at example code in mod_macro and mod_perl that does this type of
thing. The code to add a block isn't nearly as clean as code to add a
Encouraged, although if we do overhaul the parser from two to three passes
you might have a bit of porting work, and your module probably
won't remain compatible with most apache 'configurators'.
So it goes.
If you are doing your own thing, look at macro or perl modules.
If you are
The syntax for ap_register_output_filter() specifies the handler 'key' used
in the AddOutputFilter configuration directive. The ap_hook_handler() call
does not specify the handler key from the corresponding AddHandler
configuration directive. As a consequence, the specified handler function
must
... The ap_hook_handler() call
does not specify the handler key from the corresponding AddHandler
configuration directive. As a consequence, the specified handler
function
must look at and accept or decline each request
I'm looking at trace
statements and my handler must reject
A FAQ Wiki might be useful. Then we could copy chunks of emails into the
wiki and later reference the wiki pages by URL. This would be a temporary
collecting point for the data pending formal documentation, and as such
might help to organize it.
mma
-Original Message-
From: Jeff
Apache 2.0.46, W2K
I've been working on a module and quite unexpectedly I found that my
AddHandler directive was taking affect at a global level even though it was
defined within a virtual host block. So it was affecting Apache manual
pages that weren't in the virtual host for which I had
I've been working on a module and quite unexpectedly I found that my
AddHandler directive was taking affect at a global level even
though it was
defined within a virtual host block. So it was affecting Apache manual
pages that weren't in the virtual host for which I had created the
