maybe your credentials are cached by the browser and it sends these automatically (before the auth header from the JavaScript). Try to delete all cached passwords from the browser and if the same error occurs then try to contact the Ba´kal developer.

CalDavZAP simply sends one line (Authorization: ...) in the request header, so there is really no place for auth related errors ... all auth related code (see  webdav_protocol.js) looks very similar to:

if(globalSettings.usejqueryauth!=true && xxxUsername!='' && xxxPassword!='')
req.setRequestHeader('Authorization', basicAuth(xxxUsername, xxxPassword));


On 26 Feb 2014, at 21:04, Dr. Johannes Zellner <johannes@zellner.org> wrote:


I observed something strange with caldavzap which I wasn't able to track down myself.

If I use a baikal server with auth digest and have "var globalUseJqueryAuth=true" in config.js, everything works as expected and w/o errors.

If I switch to basic auth with the very same server and have globalUseJqueryAuth undefined in config.js, the initial loading of the calendar data works as expected. But after globalSyncResourcesInterval I get errors like this:

REPORT http://mysite/cal.php/calendars/username/default/ 403 (Forbidden) jquery-2.1.0.min.js:4
l.cors.a.crossDomain.send jquery-2.1.0.min.js:4
o.extend.ajax jquery-2.1.0.min.js:4
CalDAVnetLoadCollection webdav_protocol.js:2063
CalDAVnetLoadCollection.$.ajax.complete webdav_protocol.js:2337
j jquery-2.1.0.min.js:2
k.fireWith jquery-2.1.0.min.js:2
x jquery-2.1.0.min.js:4
(anonymous function)

To be clear -- I don't get these errors with auth digest.

Any ideas?