Le 30/03/2012 à 0:32, ron.vandenbranden@home a écrit :
Thanks, Igor. On Mar 30, 2012 8:41 AM, "Igor Cicimov" <icicimov@xxxxxxxxx <mailto:icicimov@xxxxxxxxx>> wrote:tcpdump -vvv -X -s 0 -i eth0 tcp port 8080 Needs to be run as root. Replace port 8080 with what ever port you need. Option "-i eth0" is just in case you have more than one network interfaces. If you use it make sure to replace eth0 with correct value for your server.Hmm, tcpdump returns nothing for reverse proxied requests: while <http://mydomain/apps/my_app/> is correctly proxied to <http://localhost:8082/my_app/>, nothing of this is traced by tcpdump.
Hi,This is probably because the proxied requests are using the "loopback" interface, so in order to capture both dialogues (between your client and your "proxy" vhost, and between your "proxy" vhost and your app vhost, you need to use the "any" pseudo-interface (meaning all the interfaces than can be found on your machine), and monitor both ports (8080 and 8082):
tcpdump -vvv -X -s 0 -i any port 8080 or port 8082If you're only interested in proxied requests, then using the "lo" interface and asking for what's using port 8082 is sufficient:
tcpdump -vvv -X -s 0 -i lo port 8082 Best regards, Bruno -- - Service Hydrographique et Oceanographique de la Marine - DMGS/INF - 13, rue du Chatellier - CS 92803 - 29228 Brest Cedex 2, FRANCE - Phone: +33 2 98 22 17 49 - Email: Bruno.Treguier@xxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|