Hi,
regarding the documentation I have to use the crossDomain attribute, if I want to use a caldavzap installation with the URL "https://xxx.aaa.com:443/calclient", which should use a Davical installation at URL "https://yyy.aaa.com:443/".
I set the crossDomain attribute to "true", but the installation is not working. The Apache2 logging says, that there is an request to URL "https://xxx.aaa.com:443/caldav.php/", but this is wrong.
What is the correct setup for this scenario? Must I use the hrefLabel attribute or something else? I also tried to modify the Apache2 Vhost config for the Davical vhost (generic allow rule), but this is not working either.
Any ideas?
Thanks and kind regards, Thomas
Hi Thomas,
On Mar 26, 2013, at 10:53 AM, Thomas W. mail@weuffel.com wrote:
Hi,
regarding the documentation I have to use the crossDomain attribute, if I want to use a caldavzap installation with the URL "https://xxx.aaa.com:443/calclient", which should use a Davical installation at URL "https://yyy.aaa.com:443/".
I set the crossDomain attribute to "true", but the installation is not working. The Apache2 logging says, that there is an request to URL "https://xxx.aaa.com:443/caldav.php/", but this is wrong.
you need to: - set the href option to correct value (from your example: "https://yyy.aaa.com:443/caldav.php/") - the default config expects that the client is installed (or "aliased" by the server config) into the DAViCal server directory - set the crossDomain to true - and also need to set proper server headers (your server needs to send CORS headers for the browser). See the misc/config_davical.txt for example CORS headers configuration (for Apache).
JM
What is the correct setup for this scenario? Must I use the hrefLabel attribute or something else? I also tried to modify the Apache2 Vhost config for the Davical vhost (generic allow rule), but this is not working either.
Any ideas?
Thanks and kind regards, Thomas
Hi Ján,
ok, I found the problem. I had an error in the Apache2 vhost config for the Davical installation. Instead of URL "https://xxx.aaa.com" I configured the URL of the Davical installation. Now it is working as expected.
Thanks, Thomas
Am 26.03.2013 um 11:56 schrieb Ján Máté:
Hi Thomas,
On Mar 26, 2013, at 10:53 AM, Thomas W. mail@weuffel.com wrote:
Hi,
regarding the documentation I have to use the crossDomain attribute, if I want to use a caldavzap installation with the URL "https://xxx.aaa.com:443/calclient", which should use a Davical installation at URL "https://yyy.aaa.com:443/".
I set the crossDomain attribute to "true", but the installation is not working. The Apache2 logging says, that there is an request to URL "https://xxx.aaa.com:443/caldav.php/", but this is wrong.
you need to:
- set the href option to correct value (from your example: "https://yyy.aaa.com:443/caldav.php/") - the default config expects that the client is installed (or "aliased" by the server config) into the DAViCal server directory
- set the crossDomain to true
- and also need to set proper server headers (your server needs to send CORS headers for the browser). See the misc/config_davical.txt for example CORS headers configuration (for Apache).
JM
What is the correct setup for this scenario? Must I use the hrefLabel attribute or something else? I also tried to modify the Apache2 Vhost config for the Davical vhost (generic allow rule), but this is not working either.
Any ideas?
Thanks and kind regards, Thomas
-
Ján Máté -
Thomas W.