Re: [us...@httpd] Capturing server response

2009-02-06 Thread anson ho
son ho" > Sent: Friday, February 06, 2009 9:53 PM > To: > Subject: Re: [us...@httpd] Capturing server response > >> mod_trace_output do exactly what you want, except that headers are not >> saved. But you can do it by myself with the source included. >> >&g

Re: [us...@httpd] Capturing server response

2009-02-06 Thread Solutio at Gmail
, assuming it's trivial. -- From: "anson ho" Sent: Friday, February 06, 2009 9:53 PM To: Subject: Re: [us...@httpd] Capturing server response mod_trace_output do exactly what you want, except that headers are not saved. But you can

Re: [us...@httpd] Capturing server response

2009-02-06 Thread anson ho
day, February 01, 2009 3:46 AM > To: > Subject: Re: [us...@httpd] CAPTURING SERVER RESPONSE > >> Solutio at Gmail wrote: >>> >>> Hi Everybody, >>> >>> I wonder if there is a way to capture the entire Apache response, >>> including its bod

Re: [us...@httpd] Capturing server response

2009-02-01 Thread André Warnier
Eric Covener wrote: On Sun, Feb 1, 2009 at 3:08 PM, Solutio at Gmail wrote: Gotcha. I haven't had to do that before, but I am sure I will figure that out. We will try this solution as well as setting up a proxy, to see which will have the least impact on the overall performance. Thanks heaps.

Re: [us...@httpd] Capturing server response

2009-02-01 Thread Eric Covener
On Sun, Feb 1, 2009 at 3:08 PM, Solutio at Gmail wrote: > Gotcha. I haven't had to do that before, but I am sure I will figure that > out. We will try this solution as well as setting up a proxy, to see which > will have the least impact on the overall performance. Thanks heaps. Maybe mod_disk_ca

Re: [us...@httpd] Capturing server response

2009-02-01 Thread Solutio at Gmail
Thanks again for your help. It would have taken me countless hours to get to this point on my own... -- From: "André Warnier" Sent: Sunday, February 01, 2009 2:41 PM To: Subject: Re: [us...@httpd] Capturing server response Soluti

Re: [us...@httpd] Capturing server response

2009-02-01 Thread André Warnier
Solutio at Gmail wrote: Gotcha. I haven't had to do that before, but I am sure I will figure that out. We will try this solution as well as setting up a proxy, to see which will have the least impact on the overall performance. Thanks heaps. If you need more specific help with mod_perl, I sug

Re: [us...@httpd] Capturing server response

2009-02-01 Thread Solutio at Gmail
ré Warnier" Sent: Sunday, February 01, 2009 1:12 PM To: Subject: Re: [us...@httpd] Capturing server response Solutio at Gmail wrote: Thank you for the advice and introduction to the forum rules. I "lowercased" the subject. As for the options available, we would like to avoid sending

Re: [us...@httpd] Capturing server response

2009-02-01 Thread André Warnier
Solutio at Gmail wrote: Thank you for the advice and introduction to the forum rules. I "lowercased" the subject. As for the options available, we would like to avoid sending the same request to the web server (Apache) if possible. Sure, LWP could emulate a web client, but our goal is to fork

Re: [us...@httpd] Capturing server response

2009-02-01 Thread Solutio at Gmail
nt: Sunday, February 01, 2009 3:46 AM To: Subject: Re: [us...@httpd] CAPTURING SERVER RESPONSE Solutio at Gmail wrote: Hi Everybody, I wonder if there is a way to capture the entire Apache response, including its body, on the server side, and store it in a file, so we could check what the u

Re: [us...@httpd] CAPTURING SERVER RESPONSE

2009-02-01 Thread André Warnier
Solutio at Gmail wrote: Hi Everybody, I wonder if there is a way to capture the entire Apache response, including its body, on the server side, and store it in a file, so we could check what the user actually gets by viewing the contents in a browser? We keep requests for audit purposes, but

[us...@httpd] CAPTURING SERVER RESPONSE

2009-01-31 Thread Solutio at Gmail
Hi Everybody, I wonder if there is a way to capture the entire Apache response, including its body, on the server side, and store it in a file, so we could check what the user actually gets by viewing the contents in a browser? We keep requests for audit purposes, but the data changes quickly,