Johan,
your working setup is non cross-domain, and the setup you want is cross-domain setup.
Check the new readme.txt with detailed cross-domain setup information/instructions ...
JM
On 27 Nov 2013, at 09:44, Johan Vromans jvromans@squirrel.nl wrote:
I have DAViCal and CalDAVzap installed on my workstation. Assume the hostname of the workstation is 'ws.mydomain.com'. I have a CNAME 'davical.mydomain.com'. The system is running Fedora 17, with apache 2.2.23.
'davical.mydomain.com' is configured as a virtual host:
<VirtualHost *:80 >
DocumentRoot /usr/share/davical/htdocs
DirectoryIndex index.php index.html
ServerName davical.mydomain.com Alias /images/ /usr/share/davical/htdocs/images/
<Directory /usr/share/davical/htdocs/> AllowOverride None Order allow,deny Allow from all
</Directory>
AcceptPathInfo On
</VirtualHost>
In the CalDAVzap config, I use the following settings:
var globalNetworkCheckSettings = undefined; var globalAccountSettings = [ { href: 'http://davical.mydomain.com/caldav.php/jv/', hrefLabel: null, crossDomain: true, forceReadOnly: null, withCredentials: true, showHeader: true, userAuth: { userName: 'jv', userPassword: '******' }, syncInterval: 60000, timeOut: 30000, lockTimeOut: 10000, delegation: false, // CalDAVzap specific. settingsAccount: true, ignoreAlarms: false, backgroundCalendars: [] } ];
CalDAVzap is accesed via an alias in the httpd.conf:
Alias /caldavzap /home/jv/wrk/CalDAVzap/caldavzap
This works great as long as I use
http://davical.mydomain.com/caldavzap/
(which surprises me -- I'd expect a virtual host to take precedence over an alias)
But it doesn't work if I use
http://ws.mydomain.com/caldavzap/
which is the way I'd want it to work, in particular since I need to move davical to a separate server.
Any ideas what I'm doing wrong?
-- Johan