Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 3811] New: Wireshark doesn't decode WBXML/ActiveSync infor

Date: Wed, 5 Aug 2009 09:22:15 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3811

           Summary: Wireshark doesn't decode WBXML/ActiveSync information
                    correctly.
           Product: Wireshark
           Version: 1.2.1
          Platform: Other
        OS/Version: Windows Vista
            Status: NEW
          Severity: Major
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: florian@xxxxxxxxxx


Build Information:
Got a port-80 capture of a ActiveSync session between a Windows Mobile device
and Microsoft Exchange Server 2007. most of the session isn't decoded. Part of
the reason seems to be that the Wireshark decoders seem to expect a
Content-type of application/vnd.ms-sync.WBXML, however the MS-Spec found at
http://msdn.microsoft.com/en-us/library/dd299446.aspx specifies that this can
be short-handed as appliation/vnd.ms-sync

2.2.1.1.2.2   Content-Type 
The Content-Type header indicates the format of the data sent in the request
body. The request body is in WBXML format and a Content-Type header value of
application/vnd.ms-sync.WBXML or the shortened string application/vnd.ms-sync
would reflect the same information. For more details about Content-Type header,
see [MS-ASCMD].

Not sure if other issues exist down the road, but that's the initial block.
--


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.