I see, the problem is not wbxml at all it is due to the fact that our
HTTP implementation does not support having the header in one packet
and the body in another. Oddly enough if either the header or the body
were split between two packets it had dissected it.
I opened http://bugs.wireshark.org/
Luis,
I used editcap to include the two TCP packets that make up the wbxml
flow.
Thnax,
gerry
wbxml.pcap
Description: wbxml.pcap
___
Wireshark-users mailing list
Wireshark-users@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-users
Well "application/vnd.syncml+wbxml" IS registered in the "media_type"
table http uses tom select the dissector for the payload.That is it
SHOULD be dissected.
Why don't you send us a (small) capture file where there's wbxml and
it is not dissected so we can see what is going wrong?
Luis
On 3/6/0
Anyone? I'm still in need of help with seeing wbxml via HTTP transport.
___
Wireshark-users mailing list
Wireshark-users@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-users
I've got a trace of wbxml data going over a HTTP connection. It shows
the first TCP packet with POST and a HTTP header of
Content-type: application/vnd.syncml+wbxml
There is a TCP continuation packet that contains the POST data with the
xbxml data.
What I can't figure out is how to use the w
