We'll look at pnotes too. Thanks again.
--
From: "Mark Hedges"
Sent: Friday, February 13, 2009 1:11 PM
To: "Solutio at Gmail"
Cc: "André Warnier" ;
Subject: Re: Capturing Apache response
I'm trying to s
d messing with Apache altogether.
>
> --
> From: "Mark Hedges"
> Sent: Friday, February 13, 2009 12:07 PM
> To: "Solutio at Gmail"
> Cc: "André Warnier" ;
> Subject: Re: Capturing Apache response
>
> >
> >
> >
> > On Tue
altogether.
--
From: "Mark Hedges"
Sent: Friday, February 13, 2009 12:07 PM
To: "Solutio at Gmail"
Cc: "André Warnier" ;
Subject: Re: Capturing Apache response
On Tue, 10 Feb 2009, Solutio at Gmail wrote:
First of all, I thank you both for y
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 wo
"André Warnier"
Sent: Tuesday, February 10, 2009 4:04 PM
To:
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.
A
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
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, li
M here.
>
>
>
>
> ------
>> From: "André Warnier"
>> Sent: Sunday, February 08, 2009 5:26 PM
>> To: "Solutio at Gmail"
>> Subject: Re: Capturing Apache response
>>
>> Hi.
>>&g
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 goo
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
http://perl.apache.org/docs/2.0/user/handlers/filters.html#Bucket
10 matches
Mail list logo
