You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Zhao Sharon-CSC002 <Sh...@motorola.com> on 2004/04/14 18:52:01 UTC
RE: How To Use TCPMonitor?
Rick,
Thank you very much for the help. We are using the HTTPS for connecting to the server port. Does TCPMon:port 2080 still work? If not, which port number should I use?
Sharon Zhao
-----Original Message-----
From: Rick Umali [mailto:rgu@TheWorld.com]
Sent: Tuesday, March 30, 2004 7:10 PM
To: axis-user@ws.apache.org
Subject: Re: How To Use TCPMonitor?
Sharon:
> Can anyone direct me how to use TCPMonitor or where to find the
> document. Which listening port I should use? I assume the target
> host is the web server.
The Axis User's Guide contains the instructions for how to use the TCPMonitor (go to the Appendix near the end of the doc):
http://ws.apache.org/axis/java/user-guide.html
I have a small example of TCPMonitor at:
http://www.rickumali.com/aws/aws-java-step-extra.html
Basically, instead of pointing your client at the server's port:
client -> server:port (80)
you'll point your client at tcpmon's port. Then you'll configure TCPMonitor to forward those requests to the destination server:
client -> tcpmon:port (2080) -> server:port (80)
Good luck!
--
Rick Umali rgu@TheWorld.com www.rickumali.com
Re: How To Use TCPMonitor?
Posted by Rick Umali <rg...@TheWorld.com>.
On Wed, Apr 14, 2004 Sharon Zhao asked:
>Thank you very much for the help. We are using the HTTPS for connecting
>to the server port. Does TCPMon:port 2080 still work? If not, which
>port number should I use?
I think the key is that you have to modify your client software to point
to a different port besides 443. This new port is the one tcpmon will
listen on. Requests on this port will get forwarded to server:443 by
tcpmon.
In your original configuration, you have this:
client -> server:port (443)
In your new configuration, you can have this:
client -> tcpmon:port (2080) -> server:port (443)
NOTE that port 2080 is completely arbitrary. You get to decide what port
number it should be. But you have to point your client to that port.
I do want to make a disclaimer: I have never tried to use tcpmon to
connect to SSL. I did a quick Google, and found this:
http://www.rtfm.com/ssldump/
This may be a more appropriate tool. I hope others on this list can
comment about tcpmon and SSL data sniffing. I don't see why tcpmon
couldn't be used, but as I mentioned, I've never tried to get this to
work.
Good luck!
--
Rick Umali rgu@TheWorld.com www.rickumali.com