https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3298
Nathan Hartwell <nhartwell@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nhartwell@xxxxxxxxx
--- Comment #1 from Nathan Hartwell <nhartwell@xxxxxxxxx> 2009-06-28 19:10:33 PDT ---
I have not found a good link which defines how the header length value within
WSP should be set so if you know of one that would be appreciated.
Looking at the captures though it appears Wireshark might be dissecting these
packets correctly in both cases. The headers length 2 byte value is not taken
into account into the actual headers length of 160 + 1 byte including the
content type value.
So in the case of the "incorrect" capture Wireshark decodes the header
correctly (cued off of the header length value) and the moves onto the XML
data. If the headers length value is set to return 162 then Wireshark actually
reports it as a malformed packet FYI.
About the only thing I can consider that would need to be changed is if the
headers length value should be set to a more appropriate display of for example
2 bytes + headers length value.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
