Hi Jim, you must copy the source code INTO /usr/share/davical/htdocs (NOT /usr/share/davical). JM

On 02 Sep 2015, at 16:56, Jim Seymour <jseymour@LinxNet.com> wrote:

Hello Ján,

I'm sorry, but your installation instructions aren't working for me at all :(

According to https://www.inf-it.com/infcloud/readme.txt my server origin and client installation origin *are* the same. And, in fact, infocloud is installed in

$ /usr/share/davical# ls -l total 24 drwxr-xr-x 5 root root 4096 Jul 30 15:42 dba drwxr-xr-x 5 root root 4096 Jul 30 15:42 htdocs drwxr-xr-x 4 root root 4096 Jul 30 15:42 inc drwxr-xr-x 8 root root 4096 Sep 2 10:35 infcloud drwxr-xr-x 26 root root 4096 Jul 30 15:42 locale drwxr-xr-x 2 root root 4096 Jul 30 15:42 scripts

First I tried (in config.js) the default setup, which claimed "works out of the box, no additional setup required." It did not work. Then I tried the example above it, setting the href to point to where caldav.php really is. No joy.

This particular server was originally just a mail server, so DocumentRoot points to SquirrelMail.

When I added DAViCal, I did

Alias /cal/ /usr/share/davical/htdocs/

<Directory /usr/share/davical/htdocs/> AllowOverride None Order allow,deny Allow from all </Directory>

And users go to

https://mail.example.com/cal/caldav.php/username/calendar

Which works just fine.

Adding

Alias /infcloud/ /usr/share/davical/infcloud/

<Directory /usr/share/davical/infcloud/> AllowOverride None Order allow,deny Allow from all </Directory>

Allows https://mail.example.com/infcloud/ to get to the login screen, but logins result in

script '/usr/share/squirrelmail/caldav.php' not found or unable to stat, referer: https://mail.example.com/infcloud/

in the error.log and

Info: [globalNetworkCheckSettings: 'https://mail.example.com/caldav.php/']: crossDomain set to: 'false' Failed to load resource: the server responded with a status of 404 (Not Found)

In the JavaScript console (Chrome).

As regards the readme.txt

Item 2 doesn't really *clearly* explain what is cross-domain and what is not. It gives examples, but does not clearly note which is which. At least not to *me*.

In config.js

The comment lines really badly need to be wrapped. I've currently got an xterm window blown out to 237 columns wide, and it's still not wide enough. Makes reading the thing very difficult. For me, anyway.

Near one example it suggests that, for cross-domain setups (which I'm still not certain I have or not): misc/config_davical.txt. That turns out to be some Apache rewrite rules... with no explanation as to what to do with them.

Regards, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>.