Hi Amol, we never tested Bedework but the latest version of CalDavZAP uses very similar (or same) requests as CardDavMATE so it should work with nearly all servers. The biggest problem is usually if you want to use cross domain setup - then you need to configure your server to send proper CORS headers (see misc/config_davical.txt for required headers). JM On Jul 26, 2013, at 10:45 AM, Amol Kulkarni <amolk112k@gmail.com> wrote:

Hello, I want to configure caldavzap to work with bedework. But according to the documents, caldavzap has not been tested with bedework. Is there any known problem in configuring caldavzap with bedework ? Has anyone tried it before ? Any hints / workaround to just get one account working for proof of concept?

Thanks in advance, Amol.

Hi Amol, your setup is cross-domain setup (because the client and server protocol+origin+port is not the same). There is a CORS specification (http://www.w3.org/TR/cors/) which says that the OPTIONS request (called also preflight request) MUST work without authorization but your server not respects this. So there are 2 possible solutions: 1.) contact the server developer and ask for fix 2.) use rewrite rules in your web server configuration - for example (for Apache): RewriteCond %{HTTP:Access-Control-Request-Method} !^$ RewriteCond %{REQUEST_METHOD} OPTIONS RewriteRule ^(.*)$ $1 [R=200,L] JM On Jul 26, 2013, at 4:19 PM, Amol Kulkarni <amolk112k@gmail.com> wrote:

Hi Jan,

I'm attaching screenshot from webconsole of firefox. It is getting an unauthorised error. Foll is my global network setting line :

var globalNetworkCheckSettings={href: 'http://192.168.0.18:8080/ucaldav/user/', hrefLabel: null, crossDomain: null, additionalResources: [], forceReadOnly: n ull, withCredentials: false, showHeader: true, settingsAccount: true, syncInterval: 60000, timeOut: 30000, lockTimeOut: 10000, delegation: false, backgroundC alendars: [], ignoreAlarms: false }

My CalDav-Zap version is 0.9.0.

Thanks, Amol.