1095001 - [Calendar] - Auto-discovery of calendars (RFC 6764, I assume) is apparently not supported

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Calendar, defect)

Description

[Ralph Daub [:rdaub]]

ENVIRONMENT:
Device Model: ZTE Open C
Version: v1.3

STEPS TO REPRODUCE:
1. Attempt to synchronize calendar with https://caldav.messagingengine.com. It supports TLS versions 1.0, 1.1 and 1.2.

EXPECTED RESULTS:
Calendar application should synchronize with the server.

ACTUAL RESULTS:
Error message "an unknown error has occurred". The user had to type out the long format for the address, so that is would synchronize correctly with the Calendar application:
https://caldav.messagingengine.com/dav/calendars/user/[e-mail]/1234a567-890b-12cd-345e-fa9b0123cdef/

SHORT USER SUMMARY:
https://support.mozilla.org/en-US/questions/1027436#answer-649262


Please let me know if there is any other information that may be helpful to investigate and troubleshoot this issue.

Thanks!

Comment 1

[Dash]

I have tried setting this up myself.

RFC 6764 https://tools.ietf.org/html/rfc6764 allows for the auto-discovery and configuration of CalDAV services.  It should be possible to simply provide an email address and for calendaring to be discovered.

Basically, check DNS for _caldavs._tcp.HOSTNAME, then _caldav._tcp.HOSTNAME for non-TLS.  Upon discovery of the calendar service, it should use _caldavs._tcp.HOSTNAME TXT record to get "path=/whatever" (again falling back to non-TLS service).  If no TXT records are found then using /.well-known/caldav to get a HTTP redirect to the correct resource.

Same applies for CardDAV, which is probably a separate bug.

Given this has sat here for two years untouched, I can't see it being picked up.  But thought I'd add a bit of info.

Comment 2

[BMO Automation]

Firefox OS is not being worked on