[Tickets #14733] Re: Send status 12 instead of http error 500 (eas v14.0) if requesting non-existing collectionId with syncKey != 0

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14733
------------------------------------------------------------------------------
  Ticket             | 14733
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Send status 12 instead of http error 500 (eas v14.0) if
                     | requesting non-existing collectionId with syncKey != 0
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2017-11-19 05:45) wrote:

I cannot reproduce this, even with TbSync.

The only way I can get TbSync to issue a SYNC for a collection that  
does not exist is to delete one of the already synchronized folders  
from Horde. The next time TbSync synchronizes, it seems to always  
issues a FOLDERSYNC which, correctly, sends back the fact that the  
folder was deleted. Therefore, the client should never (and TbSync  
does not) issue the SYNC command with the non-existent collection.

If a SYNC was issued prior to the client receiving a FOLDERSYNC  
response indicating it was removed, the Horde server should send back  
a status 12, and from all the code paths I can trace, it seems to do  
just that. If you have a step-by-step way of reproducing this or (even  
better) you can provide a unit test that fails, I can investigate  
further. Until then, I am closing this ticket as non-reproducible.