this entails pointing your test suite to a different port, and with WLI test client (Web) this doesn't work because they hardcode the portnumber in the HTTP Response (smart!).
Perhaps using this trick http://tompson.wordpress.com/2006/12/20/tcp-monitor-plugin-for-eclipse/ of pointing the JVM to use the TCP mon as a proxy (
-Dhttp.proxyHost=localhost -Dhttp.proxyPort=8080)
you can make it work...I have tried this PortPeeker port traffic monitoring tool:
http://www.gold-software.com/PortPeeker-file2605.html
but it cannot examine an already opened port.... pretty useless for a sniffer tool...
Let's try then Wireshark http://www.wireshark.org/
or tcpdump / windump http://www.mirrorservice.org/sites/ftp.wiretapped.net/pub/security/packet-capture/winpcap/windump/
(both Wireshark and WinDumo use WinpCap libraries to capture traffic)
No comments:
Post a Comment