Hi,
On Feb 12, 2013, at 10:31 PM, Sven Anders anders@anduras.de wrote:
I think I configured it correctly. Here the headers:
OPTIONS /caldav.php/ HTTP/1.1 Host: caldav.hannover.anduras.office User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: de-de,de;q=0.8,en-us;q=0.5,en;q=0.3 Accept-Encoding: gzip, deflate Origin: http://calendar.hannover.anduras.office Access-Control-Request-Method: PROPFIND Access-Control-Request-Headers: authorization,content-type,depth,x-client Connection: keep-alive
HTTP/1.1 200 OK Date: Tue, 12 Feb 2013 21:13:30 GMT Server: Apache/2.2.22 (Ubuntu) Access-Control-Allow-Origin: http://calendar.hannover.anduras.office, http://calendar, http://addressbook.hannover.anduras.office, http://addressbook Access-Control-Allow-Methods: GET,POST,OPTIONS,PROPFIND,REPORT,PUT,MOVE,DELETE,LOCK,UNLOCK Access-Control-Allow-Headers: User-Agent,Authorization,Content-type,Depth,If-match,If-None-Match,Lock-Token,Timeout,Destination,Overwrite,X-client,X-Requested-With access-control-allow-credentials: true Content-Length: 618 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html; charset=iso-8859-1
Do you see anything wrong here?
Yes - it is wrong. You cannot use Access-Control-Allow-Origin with multiple origins separated by comma ... if you really need to allow multiple origins, you need to define them separately:
.... Header always set Access-Control-Allow-Origin http://calendar.hannover.anduras.office Header always set Access-Control-Allow-Origin http://calendar Header always set Access-Control-Allow-Origin http://addressbook.hannover.anduras.office Header always set Access-Control-Allow-Origin http://addressbook ....
** Some more questions:
CalDavZap
- How do I add calenders of other people?
a.) both globalAccountSettings and globalNetworkAccountSettings allows you to define an array of accounts b.) both globalAccountSettings and globalNetworkAccountSettings allows you to define an array of additionalResources for each account c.) globalNetworkAccountSettings with auth module allows you to define any configuration dynamically (in the auth module itself) d.) you can use the delegation option (in globalAccountSettings, globalNetworkAccountSettings and also the combination of the globalNetworkAccountSettings and the auth module)
it the config.js there are a ton of comments (with examples) for each of these options ... currently the config.js (with combination of the changelog.txt) is the "best" documentation ;-)
- Is it possible to change the calendar color?
no, CalDavZAP reads the calendar color from the server (it is stored by Apple clients as a property - "http://apple.com/ns/ical/calendar-color") ... if there is no such property on the server then CalDavZAP generates a color from the calendar URL (so it is always the same, but you cannot change it in the client itself)
- Is it possible to hide completed TODOs?
currently you can use the globalTodoHideExpired option (see config.js) ... but in 0.9 we will add a completely new interface for TODO with lot of new options (0.9 is coming in ~3 weeks)
CardDavMate
- How do I create Groups?
this feature is supported ONLY by Apple clients (there is no resource/collection management in the current version of CardDavMATE/CalDavZAP) ... but CardDavMATE has full read-write support for vCard groups (if these are already defined)
- Is it possible to filter by categories?
directly not, but you can use the search box
** Some ideas for usability:
CardDavMate
- Make the image (in edit mode) clickable and show a upload window.
this feature is already on my roadmap
- Autocomplete for already used categories or display select list/box.
this feature is already present ... if you start to write the category name you will see a listbox for categories with similar names ... you can also press the "down" button on your keyboard to see all currently present categories
JM