@sfroemer Thanks for the update, so I don’t have to answer via email 😉
Can not connect to yandex caldav
I have no connection issues with AndroidCaldavSyncAdapater and CalDAV-Sync(http://dmfs.org/wiki/index.php?title=Yandex).
What I’m doing wrong? I need some help
Thanks in advance
here is a catlog:
03-04 16:13:23.499 I/davdroid.QueryServerDialogFragment(29510): onCreateLoader
03-04 16:13:23.499 I/davdroid.WebDavResource(29510): Using preemptive authentication (not compatible with Digest auth)
03-04 16:13:23.839 D/davdroid.SNISocketFactory(29510): Setting SNI hostname
03-04 16:13:24.150 I/davdroid.SNISocketFactory(29510): Established TLSv1 connection with caldav.yandex.ru using SSL_RSA_WITH_RC4_128_SHA
03-04 16:13:24.350 D/davdroid.WebDavResource(29510): Received HTTP/1.1 200 OK
i can provide with a testing yandex account, if somebody could debug it
I have created a test account, but it doesn’t work in any clients. Can you please send the test account to firstname.lastname@example.org?
Thanks for reply! I’ll send you an email with test account
I’ll send you an email with login data for a test account
Thanks in advance!
$ curl -vX OPTIONS -u $username:$password https://caldav.yandex.ru * Rebuilt URL to: https://caldav.yandex.ru/ * Adding handle: conn: 0x1faadc0 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0x1faadc0) send_pipe: 1, recv_pipe: 0 * About to connect() to caldav.yandex.ru port 443 (#0) * Trying 184.108.40.206... * Connected to caldav.yandex.ru (220.127.116.11) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSL connection using SSL_RSA_WITH_RC4_128_SHA * Server certificate: * subject: Eemail@example.com,CN=caldav.yandex.ru,ST=Russian Federation,L=Moscow,OU=ITO,O=Yandex LLC,C=RU * start date: Nov 28 14:26:26 2013 GMT * expire date: Nov 27 14:26:26 2016 GMT * common name: caldav.yandex.ru * issuer: CN=Certum Level IV CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL * Server auth using Basic with user 'firstname.lastname@example.org' > OPTIONS / HTTP/1.1 > Authorization: Basic XXXXXXXXXXXXXXXXXXXXXXX > User-Agent: curl/7.32.0 > Host: caldav.yandex.ru > Accept: */* > < HTTP/1.1 200 OK * Server nginx is not blacklisted < Server: nginx < Date: Sat, 15 Mar 2014 11:52:02 GMT < Content-Length: 0 < Connection: keep-alive < X-Request-Id: MX4MpOz1_01g < DAV: 1,addressbook,calendar-access,calendar-auto-schedule,calendar-availability,calendar-schedule,calendar-proxy,calendarserver-private-comments,calendarserver-principal-property-search < Allow: OPTIONS, GET, HEAD, POST, TRACE, PROPFIND, PROPPATCH, MKCOL, COPY, PUT, DELETE, MOVE, LOCK, UNLOCK < MS-Author-Via: DAV < * Connection #0 to host caldav.yandex.ru left intact
As you can see, there’s no
Allow: REPORTalthough this is required for CalDAV/CardDAV synchronization.
This issue is similar to https://github.com/rfc2822/davdroid/issues/87
I have sent a bug report via the Yandex contact form.
From Yandex support:
The method REPORT has been added to the list of supported.
However, it doesn’t seem to be fixed in the public version yet.
It seems like Yandex.ru have committed their fix; it’s now working without any changes in DAVdroid.
We will add Yandex to the Configuration page soon.
Please update the Configuration page - there is now “Phone contacts” group in Contacts of Yandex Webmail which is syncing over CardDAV.
@ar-lex Thank you, I can confirm that caldav.yandex.ru is now working together with DAVdroid 0.6.1. We will add it to the Configuration page.