SOAP HTTP Calls are not recognized

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

soap

asked 14 Aug '12, 07:52

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

One Answer:

oldest newest most voted

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

link

answered 14 Aug '12, 16:08

Kurt Knochner
8.2k●4●18●75
accept rate: 15%

Your answer

toggle preview

community wiki

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

*italic* or _italic_
**bold** or __bold__
link:[text](http://url.com/ "Title")
image?![alt text](/path/img.jpg "Title")
numbered list: 1. Foo 2. Bar
to add a line break simply add two spaces to where you would like the new line to be.
basic HTML tags are also supported

learn more about Markdown

Tags:

soap ×10

Asked: 14 Aug '12, 07:52

Seen: 520 times

Last updated: 14 Aug '12, 16:08

SOAP HTTP Calls are not recognized

Follow this question

You have a trillion packets.

You need to see four of them.

Don't have Wireshark?

Related questions