Getting "does not seem to accept DAV requests" with Kolab

dengste / org-caldav

Caldav sync for Emacs orgmode

GNU General Public License v3.0

727 stars 105 forks source link

Getting "does not seem to accept DAV requests" with Kolab #80

Open msjoberg opened 9 years ago

msjoberg commented 9 years ago

I'm using the mykolab.com service, and their CalDAV works fine with other clients (DAVDroid, Thunderbird), but with org-caldav I'm consistently getting this error:

org-caldav-check-connection: The URL https://apps.kolabnow.com/calendars/myaccount%40mykolab.com/path_to_calendar/ does not seem to accept DAV requests

And it does not work on subsequent tries as in issue #30. That same URL works fine e.g. in cadaver as well (in addition to the regular CalDAV clients mentioned) I have tracked it down this far:

org-caldav-check-connection calls (url-dav-supported-p url) which fails with nil
this in turn calls (url-http-options url) which returns only (methods (GET HEAD POST OPTIONS)), i.e. does not contain the dav property - which causes url-dav-supported-p to return nil

I'm running Emacs 24.4.1 (Debian jessie version) and org-caldav is 20150131.152, i.e. newest from melpa.

Adocentyn commented 9 years ago

I can reproduce the issue on Emacs 24.5 Arch Linux (as well as with previous 24.x versions).

br4ndur commented 9 years ago

I have the same problem on Emacs 24.5 Arch Linux

shymega commented 8 years ago

I can confirm that I also have this problem with my Baikal CardDAV and CalDAV server, connected from GNU Emacs 24.5 on Gentoo 64-bit.

Additionally, other clients work fine, such as DAVDroid or vdirsyncer.

pauljamesharper commented 8 years ago

I am getting the same as above. Also on Debian Jessie with org-caldav 20160306.123

I also have it working in DavDroid and IceDove (Debian's rebranded version of Thunderbird).

Is there a workaround?

I have also raised a support Ticket with MyKolab Tech Support in case the problem is from their side.

labraven commented 8 years ago

I am getting the same. Caldav was installed from MELPA today. GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.16.6) of 2015-09-17 on lgw01-52, modified by Debian

pauljamesharper commented 8 years ago

I just submitted a bug on the Kolab.org site:

https://issues.kolab.org/show_bug.cgi?id=5394

shymega commented 8 years ago

Just wanted to add - I'm not having this issue anymore, at least with my Baikal server. Not sure what's fixed it, but it works great now. I'll check the commit history later to see if there's been anything that might have resolved the issue.

Cadair commented 8 years ago

I am also getting this issue with kolab.

OS: gnu/linux (Arch Linux)
Emacs: 24.5.1

Adocentyn commented 8 years ago

I just wanted to report that as of today (18th of September 2016), after having upgraded to Emacs 25.1, I no longer have this issue. Still unsure what this was all about...

Cadair commented 8 years ago

@Adocentyn Are you using Kolab Now or some other host? What version of Kolab is it? I am still getting the issue.

Adocentyn commented 8 years ago

@Cadair : I'm using Kolab Now so it's the "original" Kolab SaaS service. I truly don't understand what the problem could be, since this problem does not seem to have any real pattern behind its random reproductibility.

Cadair commented 8 years ago

This is also now working for me.

dengste commented 7 years ago

If some of you still have problems please use latest org-caldav to see where exactly the check for DAV is failing.

msjoberg commented 7 years ago

At least I am not using Kolab anymore, so I cannot test.