[GH-ISSUE #204] REV Property not updated on sync #668

New issue

Closed

opened 2026-03-01 17:40:47 +03:00 by kerem · 3 comments

kerem commented

2026-03-01 17:40:47 +03:00

Owner

Originally created by @mmfriedel on GitHub (Aug 3, 2017).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/204

The REV: property is not updated when I change a contact in Outlook.

I did the following. Created a contact on my CarDav server. Synced it to outlook. Edited in Outlook (added email) and waited until is was synced back.
The REV property was still that of the original contact.

The REV property should not stay the same if the content of the vCard changes.
See RFC 6350

Originally created by @mmfriedel on GitHub (Aug 3, 2017). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/204 The REV: property is not updated when I change a contact in Outlook. I did the following. Created a contact on my CarDav server. Synced it to outlook. Edited in Outlook (added email) and waited until is was synced back. The REV property was still that of the original contact. The REV property should not stay the same if the content of the vCard changes. See [RFC 6350](https://tools.ietf.org/html/rfc6350#section-6.7.4)

kerem closed this issue

2026-03-01 17:40:47 +03:00

kerem commented

2026-03-01 17:40:48 +03:00

Author

Owner

@aluxnimm commented on GitHub (Aug 3, 2017):

what server are you using and what timestamp format is written to the REV property?

But you are right we aren't writing/updating REV yet and should do so.

@aluxnimm commented on GitHub (Aug 3, 2017): what server are you using and what timestamp format is written to the REV property? But you are right we aren't writing/updating REV yet and should do so.

kerem commented

2026-03-01 17:40:48 +03:00

Author

Owner

@mmfriedel commented on GitHub (Aug 3, 2017):

I have several servers. saber/dav , CalendarServer.
The REV: property is either

REV:2017-07-23T21:30:21Z
or
REV:2017072323021Z

mostly the latter.

Michael

On Aug 3, 2017, at 3:48 PM, Alex Nimmervoll notifications@github.com wrote:

what server are you using and what timestamp format is written to the REV property?

But you are right we aren't writing/updating REV yet and should do so.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/204#issuecomment-320071518, or mute the thread https://github.com/notifications/unsubscribe-auth/ARpPagiNgfc148jVJg8g4e6mVCymwD6oks5sUiQQgaJpZM4Os3Bk.

@mmfriedel commented on GitHub (Aug 3, 2017): I have several servers. saber/dav , CalendarServer. The REV: property is either REV:2017-07-23T21:30:21Z or REV:2017072323021Z mostly the latter. Michael > On Aug 3, 2017, at 3:48 PM, Alex Nimmervoll <notifications@github.com> wrote: > > what server are you using and what timestamp format is written to the REV property? > > But you are right we aren't writing/updating REV yet and should do so. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub <https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/204#issuecomment-320071518>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ARpPagiNgfc148jVJg8g4e6mVCymwD6oks5sUiQQgaJpZM4Os3Bk>. >

kerem commented

2026-03-01 17:40:48 +03:00

Author

Owner

@aluxnimm commented on GitHub (Aug 4, 2017):

Fixed in 0b2189c , will be in next release.

@aluxnimm commented on GitHub (Aug 4, 2017): Fixed in 0b2189c , will be in next release.