I define a generalized output filter for any .page file:
SetHandler perl-script
PerlOutputFilterHandler Layout
I have a block:
DataSources Environment
which I'm referencing via an Alias from a VirtualHost:
ServerName home.Dimension.org
Docu
Geoffrey Young wrote:
My PerlResponseHandler works fine on files in the /tools directory for
pages that are specified, for example:
/tools/environment.page
/tools/index.page
If I use just the directory URI:
/tools/
the DirectoryIndex specification works but I don't get any configuration
data
know.
Thanks for all the various suggestions. This has all been very informative.
Marc M. Adkins
I define a generalized output filter for any .page file:
SetHandler perl-script
PerlOutputFilterHandler Layout
I have a block:
DataSources Environment
whic
allest
possible footprint to make it easy to review, for them what has the time
and interest.
Failing that, perhaps this IS a good solution and may benefit some other
poor soul.
Marc M. Adkins
mod_perl_config.czf
Description: Binary data
ing that I should be
able to hang the XML object (not the text representation thereof) on the
request object and avoid the overhead of printing the XML and then
parsing it again. Has anyone tried doing this?
Marc M. Adkins
Well, I _am_ using XSLT for my template expansion. That kind of makes
XML important.
Thanks for the responses, and that's about what I figured I would try.
Just wondering if anyone would answer "no it won't work because..."
John Drago wrote:
--- John ORourke <[EMAIL PROTECTED]> wrote:
I'v
wrote:
On Sat, 07 Jul 2007 11:13:49 -0700
"Marc M. Adkins" <[EMAIL PROTECTED]> wrote:
I have been struggling with DirectoryIndex behavior and configuration
information from custom Perl directives for a while now. I've been
scanning the web and posting here and thanks for th
I'm trying to cause a 404 error from an output filter and it isn't doing
what I expect. Is this even possible?
mma
Hmmm...it's a bucket brigade FilterRequestHandler output filter. It
seems to not care what return code I use, whatever is in the bucket
brigade goes out. Can I not return Apache2::Const::NOT_FOUND from
handler()? That seems odd.
Marc M. Adkins wrote:
I'm trying to cause a 404 err
Thanks in advance for any hints.
mma
Marc M. Adkins wrote:
Hmmm...it's a bucket brigade FilterRequestHandler output filter. It
seems to not care what return code I use, whatever is in the bucket
brigade goes out. Can I not return Apache2::Const::NOT_FOUND from
handler()? That seems o
possible
though, somehow.
That said you might be better served catching whatever situation is
causing you to want to do this earlier in the request cycle and keeping
the response phase from doing whatever it wants to do in the first place
and just causing the 404 to happen then.
Adam
Mar
I'm actually thinking the same thing. I've been looking for a
configuration setting that will just notice that the file isn't there
and 404, but I think the fact that there IS a response handler is
causing Apache to skip the check for the existence of the file. Failing
a simpler configuration
Implemented Fixup handler and it works fine. Thanks all.
Marc M. Adkins wrote:
I'm actually thinking the same thing. I've been looking for a
configuration setting that will just notice that the file isn't there
and 404, but I think the fact that there IS a response handler is
13 matches
Mail list logo