Hi,
On 24 Sep 2015, at 11:48, Klaus Gaßner kg@waldpfa.de wrote:
Hi!
Am 22.09.2015 18:44, schrieb Ján Máté:
Even if I don't think that this is your problem, It is not recommended to use CalDavZAP with additional authentication (e.g. custom .htaccess). If you want to use authentication use the login screen (and password manager which can pre-fill your password).
Using globalAccountSettings, this would give anyone free access to my config.js which holds my password in clear text. Not a good idea.
the reason why you should use globalNetworkCheckSettings (and not globalAccountSettings).
Ask Radicale developer for CORS support and all your problems will be solved without ProxyPass and/or similar hacks ...
So are you saying that while Lightning, Outlook and CalDavSync work fine with this setup, CalDavZAP cannot handle it and would need a different server setup?
So it makes no sense to try and find out why CalDavZAP tries to access an URL which is nowhere in the configuration?
All the apps you mentioned are native applications and not JavaScript clients (none of them have CORS limitations). Most of them are simple WebDAV clients and don't use advanced CalDAV features (such as sync-collection REPORT with sync-token, etc.). CalDavZAP tries to use the most advanced features of CalDAV protocol, and if these not work there is a fallback to mimics "stupid client behaviour". So if something not works, it is very probably not CalDavZAP problem (you are the only person who have a "mysterious" problem with Baikal). I cannot know what/where you messed up in your web server, proxy server, CalDAV server, ... configuration - so it is REALLY HARD to say anything what can help you.
You may have completely broken HTTP cache headers (generated by your server) what can cause that the browser not downloads the modified configuration file (the reason why browser A shows something other than browser B). There is a .htaccess file which adds proper headers, but it is only for Apache and works only if it is processed by Apache (and nodody knows your configuration).
So even if I want to help you, I don't have time to analyze your whole server configuration and check where is the problem. What I know is that there are hundreds of people who have no problem even if they use Baikal ...
JM