[Tickets #14510] Re: Lightning 4.7.4 can not update Events

[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/14510
------------------------------------------------------------------------------
  Ticket           | 14510
  Aktualisiert Von | Jan Schneider <jan at horde.org>
  Zusammenfassung  | Lightning 4.7.4 can not update Events
  Warteschlange    | Kronolith
  Version          | 4.2.18
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2016-11-11 14:58) hat geschrieben:

The server doesn't actually send SEQUENCE back, though Lightning  
didn't send one in this example either. And the X-MOZ-GENERATION is a  
proprietary attribute, so Lightning cannot rely on it either.

Another difference that I discovered in these two examples is the  
following though:

CalDAV: skipping item with unmodified etag :
"dc453d85b5035f3559cb6bf085b7f488"

Looks like we don't send an updated etag value for the changed event  
for some reason. At least that's what the client thinks.