Or tcpdump -vvv -X -s 0 -i eth0 -n -w tcpdump.pcap tcp port 8080
If you want to dump into a file tcpdump.pcap to inspect it later with Wireshark. On Mar 30, 2012 8:41 AM, "Igor Cicimov" <[email protected]> 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. > On Mar 30, 2012 4:55 AM, "ron.vandenbranden@home" < > [email protected]> wrote: > >> Hi, >> >> Thanks for your detailed suggestions, Tom. >> >> On 29/03/2012 18:22, Tom Evans wrote: >> >>> On Thu, Mar 29, 2012 at 5:06 PM, Ron Van den Branden >>> <[email protected]> wrote: >>> >>>> Yet, when switching on ProxyPreserveHost, internal redirects via Tomcat >>>> fail: >>>> >>>> ProxyPreserveHost off >>>> >>> ^^^^ This should be "on" surely? >>> >> >> Ouch, my bad, sorry. Surely, 'on' is what I meant. >> >> So, what URL does your backend server generate? Does the Location >>> header, as seen by Apache, contain "http://localhost:8082/" when >>> ProxyPreserveHost is on, or does it contain something else? >>> >>> The best way to debug reverse proxying is to run tcpdump on the proxy >>> server. That way, you can see the request as the reverse proxy sees >>> it, the request as the backend sees it, the raw response generated by >>> the backend and the processed response returned by the proxy. Without >>> seeing those things, we're probably just guessing. >>> >> >> I've briefly checked: I can run tcpdump on the proxy server. Yet, I don't >> know it at all. Do you perhaps know the command to achieve the task you >> mention, so I can produce more useful reports? Un/fortunately, I'm leaving >> on holiday tomorrow; but maybe I still have some time to look into this >> tonight. >> >> Kind regards, >> >> Ron >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> users-unsubscribe@httpd.**apache.org<[email protected]> >> For additional commands, e-mail: [email protected] >> >>
