Customizing Internet Services with HeaderMatch documents About the HeaderMatch document Preserving your HeaderMatch customization Enabling CalDAV and CardDAV About the HeaderMatch document The HeaderMatch document in the Internet Services folder is used to configure Internet Services' handling of parts of the HTTP protocol for security or interoperability reasons.         Warning While the HeaderMatch document can be customized by you, we recommend you use the default HeaderMatch provided with the release unless directed by customer support or professional services to do otherwise. Changes to the HeaderMatch document can have serious effects on system security and the ability for users to connect to the system. If it is necessary to customize the HeaderMatch document, we recommend you do this with a user.HeaderMatch document as described below.         Notes If you have a default FirstClass site setup, you probably won't need to change the HeaderMatch document. You can only have one HeaderMatch document per site, or per cluster on your site. The HeaderMatch document contains full documentation about the HeaderMatch commands. Top Preserving your HeaderMatch customization During an upgrade, the HeaderMatch document may be replaced. This means that if you had customized this document, you would have to reapply your customization from the backup HeaderMatch document located in the Internet Services Archive folder. To avoid this, we recommend that you create a user.HeaderMatch document in the Internet Services folder. Use this document for your customization. It isn't overwritten during an update, and Internet Services will use it in conjunction with the HeaderMatch document. The user.HeaderMatch document uses the same rules and syntax as the HeaderMatch document, with the addition of PRE: and POST: sections. You can use the user.HeaderMatch document to: • steer users of particular operating systems, browser types and versions, or languages to specific websites or template sets on your site • tailor HTTP error responses • tailor MIME content to override the MIME Types file • set Internet Services script variables • add HeaderMatch SET and VAR variables • customize the list of available forms in the dropdown menus of the Standard template set • control which authentication mechanism Internet Services will enable. Top Enabling CalDAV and CardDAV CalDAV enables users to access their FirstClass calendar information using their mobiles' native calendar and reminder/todo applications. CardDAV enables users to access their FirstClass contacts information using their mobiles' native contacts applications. There is also support for the desktop Mac's Address Book, Calendar, and Reminder applications.         Limitations Users can't create new FirstClass calendars or contact databases from these native applications. This support works best with iOS. Android devices don't come with native CalDAV or CardDAV applications, although third-party applications can be purchased. Windows Phone applications can be made to work by connecting to a Google account, then changing the relevant fields to point to a FirstClass Internet Services using the FirstClass user ID and password (the user ID can't contain spaces). BlackBerry isn't supported. By default, CalDAV and CardDAV aren't enabled. To enable them, add this to the user.HeaderMatch document: PRE: *: SET enablewebdavfeatures = WebDAV_Basic, WebDAV_Locking, WebDAV_CalDAV, WebDAV_CardDAV If you include all these options, you are also enabling WebDAV editing and file locking. Top