I applied the caldavzap patch and the client got further along. It sees my calendars but spins trying to load them. The last request that I see if a sync-collection report. I can send telemetry of the request in the morning if you like. I *might* be able to get you access to a test account.

On 05/19/2013 05:10 PM, Ján Máté wrote:

Hi Ken,

XML requests cleanup patches for RC3 (for CardDavMATE there are also few very minor changes):

http://www.inf-it.com/fixes/caldavzap_0.9rc4x.diff http://www.inf-it.com/fixes/carddavmate_0.11rc4x.diff

Please report whether these patches solve your problem.

JM

On May 19, 2013, at 7:51 PM, Ken Murchison murch@andrew.cmu.edu wrote:

...

Just started testing this release, and found the following PROPFIND request:

<?xml version="1.0" encoding="utf-8"?><D:propfind xmlns:x3="http://apple.com/ns/ical/" xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"><D:prop><x3:calendar-color/><D:current-user-privilege-set/><D:max-image-size xmlns:Dd="urn:ietf:params:xml:ns:carddav"/><D:displayname/><D:resourcetype/><D:supported-report-set/><B:supported-calendar-component-set xmlns:B="urn:ietf:params:xml:ns:caldav"/><B:supported-calendar-component-sets xmlns:B="urn:ietf:params:xml:ns:caldav"/><D:sync-token/></D:prop></D:propfind>

• You declare the caldav namespace globally (prefixed by 'C'), but then you redeclare it locally in supported-calendar-component-set (prefixed by 'B'). This is confusing my server (which is a bug on my part), but it seems to be extra unnecessary bits on the wire.

• There is no standard caldav property named supported-calendar-component-sets (plural). Are you expecting this from some server or is it a typo? v0.9rc3 isn't showing any of my calendars and I'm wondering if this is the reason.