On Tue, 10 Feb 2009, Solutio at Gmail wrote:
First of all, I thank you both for your expert opinion on the topic. I have
never had to fiddle with this sort of Apache customization, so I'm learning in
the process...
As for the way to communicate the file name to the filter, sure, we would
.
--
From: Mark Hedges hed...@scriptdolphin.org
Sent: Friday, February 13, 2009 12:07 PM
To: Solutio at Gmail solu...@gmail.com
Cc: André Warnier a...@ice-sa.com; modperl@perl.apache.org
Subject: Re: Capturing Apache response
On Tue, 10 Feb 2009, Solutio at Gmail wrote
.
--
From: Mark Hedges hed...@scriptdolphin.org
Sent: Friday, February 13, 2009 12:07 PM
To: Solutio at Gmail solu...@gmail.com
Cc: André Warnier a...@ice-sa.com; modperl@perl.apache.org
Subject: Re: Capturing Apache response
On Tue, 10 Feb 2009, Solutio at Gmail wrote:
First of all
.
--
From: Mark Hedges hed...@scriptdolphin.org
Sent: Friday, February 13, 2009 12:07 PM
To: Solutio at Gmail solu...@gmail.com
Cc: André Warnier a...@ice-sa.com; modperl@perl.apache.org
Subject: Re: Capturing Apache response
On Tue, 10 Feb 2009, Solutio at Gmail wrote:
First
Solutio at Gmail wrote:
Thanks, your version works like a charm...but doesn't
quite meets our needs. I apologize for being too vague
regarding passing parameters on to the filter. Basically,
we would like to somehow link the location and name of the
response dump with the request data, like
Mark Hedges wrote:
[...]
Then the connection output filter can read it from there.
Remove connection and I agree, that's much cleaner than putting it in
a header.
A similar post-request PerlCleanupHandler or PerlLogHandler
could save any info needed after the request was processed.
But
a...@ice-sa.com
Sent: Tuesday, February 10, 2009 4:04 PM
To: modperl@perl.apache.org
Subject: Re: Capturing Apache response
Mark Hedges wrote:
[...]
Then the connection output filter can read it from there.
Remove connection and I agree, that's much cleaner than putting it in a
header
On Sun, 8 Feb 2009, Solutio at Gmail wrote:
I wonder if there is a workaround for this without adding
a connection filter?
Try using something like the all-in-one FilterSnoop handler
on the same page at
http://perl.apache.org/docs/2.0/user/handlers/filters.html#All_in_One_Filter
- I had good
Subject: Re: Capturing Apache response
Hi.
Sorry to top-post, but I think in this case it will be clearer.
Not being the ultimate guru, but being probably the only guy available at
this day and time, I'll try my hand, at the risk of getting contradicted by
the real gurus later.
So start
We are trying to implement a solution that would allow us to capture Apache (v.
2.0.63) responses sent to clients, each in a separate file on the server. I
added a bucket brigade based output filter that mimics an example found in
10 matches
Mail list logo
