Setup for Apple Users

From DAViCal Wiki

Contents 1 If that's all set up... 2 Notable Issues 2.1 iCal handles principal grants, not collection grants 2.2 Lookback on iPhone

The applications used on Apple devices can be made to configure simply if you set your server configuration up to cater to them:

• Running an SSL server on port 8443 or a plain HTTP server on port 8008
• Running from the root of the server
• Using mod_rewrite to translate request URLs

If you install DAViCal in a subdirectory, or run it on a port other than 8443 (SSL) or 8008 (unencrypted) then clients using the Apple devices will need to go into the advanced settings and configure the full URL, as detailed in the installation instructions for iCal and iPhone (the iPod instructions are the same as for the iPhone).

The use of mod_rewrite for URL Rewriting is explained in the Apache Config section.

If that's all set up...

When your server is properly configured with all of the above, it should be possible for users to configure iCal or iPhone by entering only:

• The server hostname
• The username
• The password

and the client should auto-discover all the rest.

Notable Issues

iCal handles principal grants, not collection grants

So you need to restrict access at the collection level after granting broader access at the principal level, and users may still see delegated calendars that they cannot actually read and/or write to.

Lookback on iPhone

If you get a blank calendar on an iPhone the standard fix seems to be to set the look back for 'Only last two weeks of events' (you still see all future events, of course). I have no idea why this might be the case, but changing that setting has so frequently fixed the problem that it has to be mentioned...