DEBUG 2015-11-18 18:27:44,644 [ VSTA_Main] Synchronizer.DataAccess.CalDavDataAccess . MoveNext - Creating entity 'https://caldav.one.com/calendars/users/x@x.x/x/8c8a723e-1eeb-4661-94a7-e0a5b8de7463.ics'
DEBUG 2015-11-18 18:27:44,892 [ VSTA_Main] hronizer.Implementation.CalDavRepository . MoveNext - Duration: 00:00:00.2777901
ERROR 2015-11-18 18:27:44,893 [ VSTA_Main] nSync.Synchronization.States.StateBase`6 . LogException -
System.Net.Http.HttpRequestException: Response status code does not indicate success: '403' ('Forbidden'). Message:
<?xml version='1.0' encoding='UTF-8'?>
<error xmlns="DAV:">
<max-attendees-per-instance xmlns="urn:ietf:params:xml:ns:caldav">100</max-attendees-per-instance>
<error-description xmlns="http://twistedmatrix.com/xml_namespace/dav/">Too many attendees in calendar data</error-description>
</error>
You are right, we should honour those max-... properties, we don't ask the server for them atm.
Ticket moved from /p/outlookcaldavsynchronizer/tickets/131/