Yes, it is fixed in 1.3.4-develop now.
I’m trying to get calDAV and cardDAV to work with a single account and the root URL of install on a Synology with Baikal. Therefore I need to configure redirects, but I can’t find out what I’m doing wrong.
I tried to add the following lines to .htaccess:
Redirect 301 /.well-known/carddav /baikal/carddav
Redirect 301 /.well-known/caldav /baikal/caldav
I also tried these lines:
RedirectMatch 301 ^/.well-known/caldav /cal.php
RedirectMatch 301 ^/.well-known/carddav /card.php
Yes, I’ve read the specific Baikal page. Here’s some more info. I’ve followed these steps:
I am pretty sure I’m doing the redirects wrong.
Which version of baikal are you installing ?
Have you tried pointing the url to the only /combined
http://example.org/baikal/html/dav.php ? Note the Upgrade instructions.
No, I’m still on Baikal 0.2.7. I will probably update though, but it’s not the cause of the problem at the moment.
I am not familiar with the synology webserver, but one last thought, then:
You are probing
http://192.168.1.19/.well-known/carddav. So the .htacces file should be at
http://192.168.1.19/.htaccess and probably redirect to
/baikal/[card/cal].phpif you not already have additional fancier redirects.
EDIT: also, you could try opening
http://192.168.1.19/.well-known/carddav in a browser and see if you get a 404 error. What is strange though, is that the webserver doesn’t tell you it didn’t find the url, but sends a
405 Method Not Allowedwhich points to a configuration problem of the webserver.
Fixed! I just updated Baikal to 0.4.5. In that version card and cal are combined in a single endpoint. So no need anymore to configure any redirects.