[Tickets #13351] Re: Activesync Error 500: FOLDERUPDATE Unmatched end tag FolderHierarchy:ParentId

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13351
------------------------------------------------------------------------------
  Ticket             | 13351
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Activesync Error 500: FOLDERUPDATE Unmatched end tag
                     | FolderHierarchy:ParentId
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-07-12 15:12) wrote:

> It seems it's not the first time a BlackBerry device has misbehaved
> https://github.com/horde/horde/commit/dd1f7c37bf6ee94c6fa13d66d56e703f8dd93021
>
> but I think the problem here has more to do with the fact that the  
> client is using a non-existent sync_key to try and perform an update.
> I don't know anything about the protocol, but it seems strange that  
> Horde is trying to honour a folderupdate request when it doesn't  
> have a sync relationship with the device first.

Horde doesn't know anything until it parses the incoming request. It'  
can't parse the incoming request because it is invalid WBXML and  
cannot understand it. Even if it DID know that the synckey was expired  
or removed, the error would still be the same because the entire WBXML  
request must be parsed before a response can be sent. Since the  
parsing would fail, the response would be the same.

Essentially, BB isn't expiring it's internal cache properly and  
continues to issue the request even though the account is no longer  
active.