[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]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14733
------------------------------------------------------------------------------
  Ticket           | 14733
  Aktualisiert Von | john.bieling at gmx.de
  Zusammenfassung  | Send status 12 instead of http error 500 (eas v14.0) if
                   | requesting non-existing collectionId with syncKey != 0
  Warteschlange    | Synchronization
  Version          | FRAMEWORK_5_2
  Typ              | Bug
  Status           | Not Reproducible
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       | Michael Rubinsky
------------------------------------------------------------------------------


john.bieling at gmx.de (2017-11-19 13:34) hat geschrieben:

Everything you say is correct. The bug cannot be triggered with the  
official TbSync. I found this only by fuzzing around.

I created a special TbSync Version, which will reproduce the error every time:
https://github.com/jobisoft/TbSync/releases/download/v0.6.8.2/TbSync_horde_bug_14733.xpi

After you connected your account, right click in the folder list  
section of the TbSync Account Manager and you will find the following  
menuitem: "add folder to list which does not exist on server with  
synckey != 0".

If you click that, a new folder "89" shows up. If you than hit the  
"Sync this account" button, the sync fails with an HTTP error 500.

All this does is sending the request I included in the very first post  
of this bug report. You can enable the debug log (under help) to see  
what is send and received by TbSync.

John