On 22 Sep 2015, at 16:41, Klaus Gaßner <firstname.lastname@example.org> wrote:
I have been trying to use Caldavzap but so far without success.
I have a Radicale server which I want to access. Server is running fine, access with Clients like Mozilla Lightning, Outlook or CalDavSync works fine. Server access is with a ProxyPass in Apache config.
I decided to use globalAccountSettings. Originally, the server's adress was http://calendar.wanderreitkarte.de/beide/calendar.ics, so I set config.js to
Caldav I put onto a different subdomain. This produced cross-domain problems. As I did not find a way to make Radicale allow the cross-domain access, I moved the caldav server one
folder down to http://calendar.wanderreitkarte.de/radicale/beide/calendar.ics/ and put CaldavZap on top level of the same subdomain.
Now my settings read
I have changed cache.manifest multiple times and I did get the message that a newer version was available and reloaded the page.
However, when I try to run Caldavzap, I get the following error messages (in Chrome):
- do you have any idea what the reason for that 405 might be?
- why does it still try to access the old URL That string is nowhere in the config.js. Or is it wrongly reconstructed from the base URL and login name for some reason?
In Firefox I get a different error message:
GET http://calendar.wanderreitkarte.de/cache_handler.js [HTTP/1.1 200 OK 108ms]
OPTIONS http://www.inf-it.com/versioncheck/CalDavZAP/ [HTTP/1.1 200 OK 120ms]
not well-formed <unknown>:1:110
Which does not look similar at all. Any ideas what causes this completely different fail?
Thanks for any advice
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.