[CalDAV] SmarterMail calendar-home-set is not a collection of calendars

While testing our app DAVdroid with the SmarterMail CalDAV/CardDAV interface, I have found that calendar-home-set specifies /WebDAV/cal as the homeset:

> PROPFIND / HTTP/1.1
> Host: mailserv.palace-designs.com
>
* upload completely sent off: 106 out of 106 bytes
< HTTP/1.1 207 Multi-Status
< Content-Type: text/xml; charset=utf-8
* Server Microsoft-IIS/8.5 is not blacklisted
< Server: Microsoft-IIS/8.5
<
<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:">
  <D:response>
    <D:href>/</D:href>
    <D:propstat>
      <D:status>HTTP/1.1 200 OK</D:status>
      <D:prop>
        <C:calendar-home-set xmlns:C="urn:ietf:params:xml:ns:caldav">
          <D:href>/WebDAV/cal</D:href>
        </C:calendar-home-set>
      </D:prop>
    </D:propstat>
  </D:response>

However, /WebDAV/cal/ seems to be the actual calendar and not a home set (which are, by RFC 4791 6.2.1, "WebDAV collections that contain calendar collections"):

> PROPFIND /WebDAV/cal HTTP/1.1
> Host: mailserv.palace-designs.com
> Depth: 1
>
< HTTP/1.1 207 Multi-Status
< Content-Type: text/xml; charset=utf-8
<
<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:">
[...]
  <D:response>
    <D:href>/WebDAV/cal/</D:href>
    <D:propstat>
      <D:status>HTTP/1.1 200 OK</D:status>
      <D:prop>
        <D:resourcepath>/WebDAV/cal/</D:resourcepath>
        <D:displayname>My Calendar</D:displayname>
        <A:calendar-color xmlns:A="http://apple.com/ns/ical/">#4b96d7</A:calendar-color>
        <D:resourcetype>
          <D:collection />
          <C:calendar xmlns:C="urn:ietf:params:xml:ns:caldav" />
        </D:resourcetype>
      </D:prop>
    </D:propstat>
  </D:response>
[...]

This will cause clients which expect calendars as collections in the home set (i.e. one level deeper) to fail when listing the calendars.

Employee Replied

11/3/2014 at 3:23 PM

Employee Post

Hi there!

Thanks for bringing this up. I know that in a future version of SmarterMail the developers plan to really focus on calendaring and address many of the issues at that time. I'm sure they'll need to look into this a bit more, but if a change is needed in the way this is implemented, it'll be addressed in that future version.

One thing to note: while we do try to develop according to RFC, please be aware that these are suggestions and not hard fast rules. That being said, we try our best to accommodate as many protocols and applications as possible, so I'll go ahead and bring this to the developers' attention as well and we'll look into this a bit more.

Thanks!

1 Reply

Reply to Thread

Related Knowledge Base Articles

1 Reply

Reply to Thread

Tags

Related Knowledge Base Articles