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. http://trace-output.sourceforge.net/ On Mon, Feb 2, 2009 at 2:56 AM, Solutio at Gmail <solutio@xxxxxxxxx> 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 the very same HTTP response that Apache > sends to the browser, into a file, rather than repeating the request. One of > the reasons being that as I mentioned, the data in the response can already > be different. > > Thanks again. > > -------------------------------------------------- > From: "André Warnier" <aw@xxxxxxxxxx> > Sent: Sunday, February 01, 2009 3:46 AM > To: <users@xxxxxxxxxxxxxxxx> > Subject: Re: 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 user actually gets by viewing the contents in a browser? We >>> keep requests for audit purposes, but the data changes quickly, and the same >>> request can result in a different response over time. I looked for ideas on >>> Google and CPAN, but haven't been able to find any definite answer so far. >>> >> Hi. >> First, just a small item relating to "etiquette" (politeness etc..) in >> forums like this one : writing something in CAPITALS is generally considered >> as equivalent to shouting. So it's not a very good idea to use that in the >> subject of your posting. >> >> About your question : >> There are may ways to capture the response of a HTTP server. The easiest >> ones consist of programs that can act as a "client" (like a browser), and >> save the answer from the server to a disk file. >> If you have perl installed wherever, I suggest to have a look at the >> "lwp-request" command, which is very flexible and allows you to tailor what >> you send to the server as well as what you want to see (or save) at the >> client level. >> In the simplest form : >> lwp-request -m GET "http://www.myserver.com/myurl"; >> or >> lwp-request -m GET "http://www.myserver.com/myurl"; > saved_file.html >> >> I suggest the above because it will run on whatever platform, as long as >> perl is inatalled on it. >> >> There are a bunch of other programs that can do similar things, including >> saving a whole website if you wish. Look at "curl", "wget" etc.. Their >> availability may depend on the platform. >> >> >> >> >> --------------------------------------------------------------------- >> The official User-To-User support forum of the Apache HTTP Server Project. >> See <URL:http://httpd.apache.org/userslist.html> for more info. >> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx >> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx >> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx >> >> > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|