This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

SOAP HTTP Calls are not recognized

0

I'm a newbe, so my question might be pretty trivial.

I have developed a SOAP client & am testing it by calling a remote server. When tracing with wire shark while issuing a call via SOAP-UI, all packages are only recognized by wireshark as 'TCP', not as HTTP or XML.

The result is that debugging is a nightmare, since I have to leave through all traffic to that destination and source IP address. Once found, i can use 'show stream' to see the entire xml message, but finding it is horror.

Am I doing something wrong? How can I configure WireShark to only show me the http/xml soap messages?

Many thanks in advance

asked 14 Aug '12, 07:52

lxkern's gravatar image

lxkern
1●1●1●1
accept rate: 0%

One Answer:

0

If your HTTP server does not run on one of the default ports (configurable for the HTTP dissector), Wireshark will not detect HTTP as such.

What can you do?

  • change the settings of the HTTP dissector. Add "your" port to the list of TCP Ports.

Edit -> Preferences -> Protocols -> HTTP -> TCP Ports

  • right click on a packet of the communication and select "Decode As". Then choose HTTP for the Transport decoding
  • Change the port of your application to one of the ports Wireshark dissects as HTTP

Regards
Kurt

answered 14 Aug '12, 16:08

Kurt%20Knochner's gravatar image

Kurt Knochner ♦
24.8k●10●39●237
accept rate: 15%