Default caldav path for calendar app?

Mon, 15 Jul 2019 21:05:57 -0700

I think I saw it once, but haven't been able to find it again. If anyone knows offhand, I would appreciate a hint.

show all 10 comments

Thu, 18 Jul 2019 20:46:14 -0700 last edited: Thu, 18 Jul 2019 20:46:53 -0700

Ok, so, I'm halfway there. The URL that is now showing both of my test calendars is:
<base URL>/cdav/principals/<channel name>/

This is being pulled by DAVx5 on my android. I was able to crib the resource url from the DAVx5 error log when I originally tried /cdav/calendars/, but that never listed my test calendars. I'm still getting a 404 whenever I try to sync, so I will have a look at that tomorrow.

Mike Macgirvin

Thu, 18 Jul 2019 21:27:57 -0700

<baseurl>/cdav/calendars/<nickname>

works for me, but for sync with lightning that needs to be followed by the actual calendar name. For instance

<baseurl>/cdav/calendars/<nickname>/home

This should be documented somewhere more useful (like the settings page) so you can find it again, and I believe I have seen it documented some place, but like you I can never seem to find it when somebody asks.

Bill Albertson

Thu, 18 Jul 2019 21:49:03 -0700

Huh. Well, I tried the URLs you listed, and the ones I listed just to be sure. So far, I'm only getting both calendars from <base URL>/cdav/principals/<channel name>/

I'll look again tomorrow when I feel more awake... maybe I need to update :)

Bill Albertson

Sat, 03 Aug 2019 12:44:05 -0700

Ok, I'm back. I've tried accessing caldav with cadaver, and all I'm getting is 404 errors, which is new and different from davx, which gave 404s but only listed files under <base URL>/cdav/principals/<channel name>.

Is it possible there is some kind of permissioning error I'm not aware of? The server access log shows a 401, and then a 404 error when accessing.


dav:!> open https://zap.exanimate.net/cdav/principals/bill    
Authentication required for Zap CalDAV/CardDAV on server `zap.exanimate.net':
Username: bill@exanimate.net
Password: 
Authentication required for Zap CalDAV/CardDAV on server `zap.exanimate.net':
Username: bill@exanimate.net
Password: 
Could not open collection:
404 Not Found
dav:/cdav/principals/bill/? exit


bills-grimoire:~> cadaver https://zap.exanimate.net/cdav/calendars/bill      
Authentication required for Zap CalDAV/CardDAV on server `zap.exanimate.net':
Username: bill@exanimate.net
Password: 
Could not open collection:
404 Not Found
dav:/cdav/calendars/bill/? exit

174.50.167.76 - - [03/Aug/2019:12:19:41 -0700] "OPTIONS /cdav/calendars/bill/ HTTP/1.1" 401 4265 "-" "cadaver/0.23.3 neon/0.30.2" 
174.50.167.76 - - [03/Aug/2019:12:20:12 -0700] "OPTIONS /cdav/calendars/bill/ HTTP/1.1" 404 956 "-" "cadaver/0.23.3 neon/0.30.2" 
174.50.167.76 - - [03/Aug/2019:12:20:57 -0700] "OPTIONS /cdav/calendars/bill/ HTTP/1.1" 401 4265 "-" "cadaver/0.23.3 neon/0.30.2" 
174.50.167.76 - - [03/Aug/2019:12:21:16 -0700] "OPTIONS /cdav/calendars/bill/ HTTP/1.1" 404 956 "-" "cadaver/0.23.3 neon/0.30.2"

Bill Albertson

Sat, 03 Aug 2019 13:25:40 -0700

Ok, so I figured out my malfunction. I didn't read the section "- 400 and 4xx "File not found" errors" of the Install.txt as carefully as I should have!

My issue is due to the odd configuration of Apache on Dreamhost. I will work out a solution and post that back later.

Mike Macgirvin

Sat, 03 Aug 2019 15:13:57 -0700

hz.macgirvin.com is on dreamhost and using the default .htaccess file supplied by Hubzilla. I get similar results with Zap (also on Dreamhost using the default .htaccess) except that I do not have any created or active caldav calendars in Zap. I do however see the default home,inbox, and outbox when accessing my calendars in zap but they are empty.

I understand that you've only had results when connecting to principals but once again I'll suggest that if you want to access calendars you should probably access calendars and not principals (people). We've never really populated the principals with anything - the entries under principals only exist to allow sharing.


% cadaver
dav:!> open https://hz.macgirvin.com/cdav/calendars/hubzilla
Authentication required for RedCalDAV/CardDAV on server `hz.macgirvin.com':
Username: hubzilla
Password: 
dav:/cdav/calendars/hubzilla/> ls
Listing collection `/cdav/calendars/hubzilla/': succeeded.
Coll:   4afb806b7f74befa9973621d20257dbc6ed8477f          0  Jan  1  1970
Coll:   default                                0  Jan  1  1970
Coll:   home                                   0  Jan  1  1970
Coll:   inbox                                  0  Jan  1  1970
Coll:   outbox                                 0  Jan  1  1970
dav:/cdav/calendars/hubzilla/> cd home
dav:/cdav/calendars/hubzilla/home/> ls
Listing collection `/cdav/calendars/hubzilla/home/': succeeded.
        a03896d419f2ffa0397a7eac6f63d81c439fb698.ics        364  Apr 17 09:52
        de33134b0ccd7e5b828b9a313ba702c2e63e7609.ics        363  Apr 17 09:51
dav:/cdav/calendars/hubzilla/home/> quit
Connection to `hz.macgirvin.com' closed.

% cadaver
dav:!> open https://hz.macgirvin.com/cdav/principals/hubzilla
Authentication required for RedCalDAV/CardDAV on server `hz.macgirvin.com':
Username: hubzilla
Password: 
dav:/cdav/principals/hubzilla/> ls
Listing collection `/cdav/principals/hubzilla/': collection is empty.
dav:/cdav/principals/hubzilla/> quit
Connection to `hz.macgirvin.com' closed.

Bill Albertson

Sat, 03 Aug 2019 21:22:22 -0700

After reading Einer and Mike, I tried cadaver at the <base url>/cdav level, and I could log in! The caldav response shows nothing is listing in the directories where I should expect to find files. Again, that makes me wonder what is going on, because I have a default calendar /cdav/calendars/bill/default and a test calendar /cdav/calendars/bill/<long id is long>.

bills-grimoire:~> cadaver
dav:!> open zap.exanimate.net/cdav
Could not parse URL `zap.exanimate.net/cdav'
dav:zap.exanimate.net/cdav? open https://zap.exanimate.net/cdav
Authentication required for Zap CalDAV/CardDAV on server `zap.exanimate.net':
Username: bill@exanimate.net
Password: 
dav:/cdav/> list
Unrecognised command. Type 'help' for a list of commands.
dav:/cdav/> help
Available commands: 
 ls         cd         pwd        put        get        mget       mput       
 edit       less       mkcol      cat        delete     rmcol      copy       
 move       lock       unlock     discover   steal      showlocks  version    
 checkin    checkout   uncheckout history    label      propnames  chexec     
 propget    propdel    propset    search     set        open       close      
 echo       quit       unset      lcd        lls        lpwd       logout     
 help       describe   about      
Aliases: rm=delete, mkdir=mkcol, mv=move, cp=copy, more=less, quit=exit=bye
dav:/cdav/> ls
Listing collection `/cdav/': succeeded.
Coll:   addressbooks                           0  Dec 31  1969
Coll:   calendars                              0  Dec 31  1969
Coll:   principals                             0  Dec 31  1969
dav:/cdav/> cd calendars
dav:/cdav/calendars/> ls
Listing collection `/cdav/calendars/': failed:
404 Not Found
dav:/cdav/calendars/> ls principals
Listing collection `/cdav/calendars/principals/': failed:
404 Not Found
dav:/cdav/calendars/> ls addressbooks
Listing collection `/cdav/calendars/addressbooks/': failed:
404 Not Found
dav:/cdav/calendars/> ls calendars/bill
Listing collection `/cdav/calendars/calendars/bill/': failed:
404 Not Found

Bill Albertson

Wed, 07 Aug 2019 21:00:05 -0700

After some more testing, I found that the phone app aCalDAV from the FDroid repository works just fine for syncing calendar data. The problem was that the prior DAVX app was making a lot of assumptions about what it *had* to see. Able to sync calendars just fine with my phone now.

Mike Macgirvin

Wed, 07 Aug 2019 21:04:44 -0700

Note for future explorers in this space: should probably log what accesses DAVX makes so we can ultimately give it whatever it wants to see.

Bill Albertson

Wed, 07 Aug 2019 21:08:23 -0700

DAVx simply wouldn't sync with an empty caldav directory either. I set one up under dreamhost, separate from my zap instance. It errored there as well. Apparently DAVx was expecting specific structures and methods of access to be in place, from what I could read in the logs. I can provide testing logs for both if you want, probably can do it on Saturday when I have more time.