Page MenuHomePhorge

A synckey that is not matching the server sync key is invalid.
AbandonedPublic

Authored by mollekopf on Jan 19 2021, 10:18 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Mar 28, 2:34 PM
Unknown Object (File)
Feb 18 2024, 8:51 AM
Unknown Object (File)
Nov 16 2023, 5:25 PM
Unknown Object (File)
Nov 8 2023, 3:26 PM
Unknown Object (File)
Nov 6 2023, 12:20 AM
Unknown Object (File)
Sep 15 2023, 12:54 AM
Subscribers
None

Details

Summary

The problem I've been running into:

  • The server sent an update to the client that the client rejected (due

to "invalid folders"

  • The client sends a sync request with an "old" synckey
  • The server should now tell the client that the synckey is invalid,

but instaed silently accepts the synckey reporting no problem.

  • The client now has a different folder set than the server, which

causes problems in Sync and Ping requests.

Diff Detail

Repository
rS syncroton
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 32746
Build 12685: arc lint + arc unit

Event Timeline

mollekopf created this revision.

This code is not supposed to be used by Kolab backend. We're using kolab_sync_backend_state::validate().