Apache – Enabling Logging for Requests Through Mod Proxy

apache-2.2debugloggingmod-proxy

Is there a way to log requests going through mod proxy? I need a way to debug my configuration, because I don't seem to be getting where I should be. I need the following information:

headers of incoming requests
what is being sent to the proxy target

Maybe a related question: is there a way to strip some headers? I tried the following:

ProxyPass         /proxy/other http://not.under.my.control/
<Location /proxy/other>
   ProxyPassReverse /
   RequestHeader unset Authorization
</Location>

I don't really know whether this is ok, because I don't see anything.

Best Answer

Another option might be mod_forensic, can easily log the request and headers etc. Beware of disk space usage though, on a heavy load web-site mod_forensic can easily produce tens of Gigs per day.

http://httpd.apache.org/docs/2.2/mod/mod_log_forensic.html

Related Solutions

Apache ProxyPass/RewriteRule with p flag: Return no content when response has multi-part content type i.e.images

Unfortunately, it looks like this application seems to play pretty fast and loose with HTTP standards - it's hard to tell what exactly is upsetting it, but some of the things that Apache is doing (like combining the two nonsense identical Accept headers into a single one) are hard to do anything about.

A couple of things to try to get the requests to be more similar, in the hopes that one of those changes will get the request to the point that it's no longer upsetting this finicky HTTP server.

SetEnv proxy-nokeepalive 1

The other main difference is the X-Forwarded- headers - they can't be disabled through configuration, but there's a patch out there to turn them off.

Barring one of these changes working, the only other option seems to be to gain more visibility into this RETS application - I don't suppose there's a way to do some good debug logging? The client also seems to be behaving a bit differently when talking to the proxy, using new connections for new requests instead of re-using its open connection. I don't suppose there's logging on the client?

Ubuntu – I can’t get the dump_io module working

1> To configure mod_dumpio you need to enable dump_io.

$ sudo a2enmod dump_io

2> in apache2.conf file write this line

LogLevel dumpio:trace7
DumpIOInput On
DumpIOOutput On

3) Then restart apache server

Best Answer

Related Solutions

Apache ProxyPass/RewriteRule with p flag: Return no content when response has multi-part content type i.e.images

Ubuntu – I can’t get the dump_io module working

Related Topic