Radicale can run on its own (default install) or behind an http server
Letting radicale run behind apache using mod_proxy is not a usual
supported configuration. See the documentation :
If radicale runs behing apache, CORS headers have to bet set on apache
side. See apache documentation (mod_headers).
If radicale runs on its own, CORS headers can be set in radicale config
file. See the documentation :
Le 2015-09-22 18:44, Ján Máté a écrit :
Even if I don't think that this is your problem,
It is not recommended
to use CalDavZAP with additional authentication (e.g. custom
If you want to use authentication use the login screen (and password
manager which can pre-fill your password).
Ask Radicale developer for CORS support and all your problems will be
solved without ProxyPass and/or similar hacks ...
> On 22 Sep 2015, at 18:28, Klaus Gaßner <kg(a)waldpfa.de> wrote:
> Of course there is a password on the caldavzap URL. Otherwise
> anybody could access my calendar.
> The browser requests the password and access is granted allright.
> This should not be the problem.
> Or does caldavzap run into a problem even though the browser is
> bye, Klaus