[Tickets #12934] Re: Synchronization problem with Kronolith

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12934
------------------------------------------------------------------------------
  Ticket             | 12934
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Synchronization problem with Kronolith
  Queue              | Kronolith
  Version            | Git master
  Type               | Bug
-State              | Unconfirmed
+State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-01-24 14:58) wrote:

Outlook is sending an invalid response according to MS's own specifications.

2014-01-24T11:12:17+01:00 DEBUG: [23761] I  <MeetingResponse:MeetingResponse>
2014-01-24T11:12:17+01:00 DEBUG: [23761] I   <MeetingResponse:Request>
2014-01-24T11:12:17+01:00 DEBUG: [23761] I    <MeetingResponse:FolderId>
2014-01-24T11:12:17+01:00 DEBUG: [23761] I      @Calendar@
2014-01-24T11:12:17+01:00 DEBUG: [23761] I    </MeetingResponse:FolderId>
2014-01-24T11:12:17+01:00 DEBUG: [23761] I    <MeetingResponse:UserResponse>
2014-01-24T11:12:17+01:00 ERR: [23761] Unmatched end tag:
2014-01-24T11:12:17+01:00 ERR: Array
(
     [1] => 1
     [2] => MeetingResponse:UserResponse
     [4] => 1
)

2014-01-24T11:12:17+01:00 ERR: Protocol Error


According to the MS-ASCMD: 6.21 MeetingResponse Request Schema, the  
UserResponse element comes before the FolderId element in a  
<xs:sequence> block. Since it is arriving in an unexpected order, the  
parsing fails. I can work around it in code since there is really no  
technical requirement to have the response value before parsing the  
folderid, other than the specs stating it must be in that sequence.

It's bad enough that different clients implement things so  
differently, but when different versions of the same client do this it  
is VERY frustrating.