I’m unable to reproduce this, using either the standard or discovered-domain modes:
$ curl -i -u robntest@fastmail.fm:******** -X PROPFIND -d '<propfind xmlns="DAV:"><prop><current-user-principal/></prop></propfind>' -H 'Content-type: text/xml' https://carddav.messagingengine.com/dav/addressbooks
HTTP/1.1 207 Multi-Status
Server: nginx
Date: Sun, 28 Dec 2014 21:37:37 GMT
Content-Type: application/xml; charset=utf-8
Content-Length: 1067
Connection: keep-alive
Vary: Accept-Encoding, Brief, Prefer
<?xml version="1.0" encoding="utf-8"?>
<multistatus xmlns="DAV:">
<response>
<href>/dav/addressbooks</href>
<propstat>
<prop>
<current-user-principal>
<href>/dav/principals/user/robntest@fastmail.fm/</href>
</current-user-principal>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
<response>
<href>/dav/addressbooks/user/robntest@fastmail.fm/Default/</href>
<propstat>
<prop>
<current-user-principal>
<href>/dav/principals/user/robntest@fastmail.fm/</href>
</current-user-principal>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
<response>
<href>/dav/addressbooks/user/robntest@fastmail.fm/Default/e6aa4532-076f-4ab8-add0-4e8afb636b7b.vcf</href>
<propstat>
<prop>
<current-user-principal>
<href>/dav/principals/user/robntest@fastmail.fm/</href>
</current-user-principal>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
</multistatus>
$ curl -i -u robntest:******** -X PROPFIND -d '<propfind xmlns="DAV:"><prop><current-user-principal/></prop></propfind>' -H 'Content-type: text/xml' https://carddav-d49.messagingengine.com/dav/addressbooks
HTTP/1.1 207 Multi-Status
Server: nginx
Date: Sun, 28 Dec 2014 21:36:07 GMT
Content-Type: application/xml; charset=utf-8
Content-Length: 1067
Connection: keep-alive
Vary: Accept-Encoding, Brief, Prefer
<?xml version="1.0" encoding="utf-8"?>
<multistatus xmlns="DAV:">
<response>
<href>/dav/addressbooks</href>
<propstat>
<prop>
<current-user-principal>
<href>/dav/principals/user/robntest@fastmail.fm/</href>
</current-user-principal>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
<response>
<href>/dav/addressbooks/user/robntest@fastmail.fm/Default/</href>
<propstat>
<prop>
<current-user-principal>
<href>/dav/principals/user/robntest@fastmail.fm/</href>
</current-user-principal>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
<response>
<href>/dav/addressbooks/user/robntest@fastmail.fm/Default/e6aa4532-076f-4ab8-add0-4e8afb636b7b.vcf</href>
<propstat>
<prop>
<current-user-principal>
<href>/dav/principals/user/robntest@fastmail.fm/</href>
</current-user-principal>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
</multistatus>
- CalDAV: Yesterday, the responses contained emails with VEVENTs instead of VEVENTs. Today, it works again (and so does DAVdroid with FastMail). So this was a FastMail problem.
This was an outright bug that we (somehow) hadn’t noticed. BusyCal reported it to us and it was fixed within a couple of hours.
I wonder why I should do debugging work for FastMail.
You shouldn’t, but you should certainly tell us when there’s a problem! We care a lot about standards compliance, but of course *DAV is going to have ridiculous bugs because its a ridiculous protocol. If you see something obviously wrong, let us know and we’ll fix it. You can @-mention me here, or email robn@fastmail.com.