= Free/Busy Publishing =

Although iTIP [[http://tools.ietf.org/html/rfc5546#section-3.3|specifies]] the exchange
of free/busy information through requests and replies, many mail-based calendar clients
do not support these particular operations over e-mail when providing general
[[http://tools.ietf.org/html/rfc6047|iMIP]] support. However, they may support the
acquisition of free/busy information over HTTP.

The publishing of free/busy resources for users can be enabled by default in the
[[../Configuration|configuration]] by changing the `PUBLISHING_DEFAULT` setting:

{{{
PUBLISHING_DEFAULT = "publish"
}}}

For this setting to have an effect, the `SHARING_DEFAULT` setting will need to be
changed to enable free/busy sharing by default:

{{{
SHARING_DEFAULT = "share"
}}}

Users can enable sharing and publishing themselves by accessing their profile in the
[[../CalendarManager|management interface]].

Depending on the [[../WebServerIntegration|Web server configuration]], resources are
made available at a location resembling the following:

{{{
https://webserver.example.com/freebusy/
}}}

Individual user data is published in locations like this:

{{{
https://webserver.example.com/freebusy/mailto%3Avincent.vole%40example.com/freebusy
}}}

Here, the `mailto:vincent.vole@example.com` identity has been URL-encoded. Web
browsers and mail programs may perform such encoding on a location given more
informally as follows:

{{{
https://webserver.example.com/freebusy/mailto:vincent.vole@example.com/freebusy
}}}

However, the properly-encoded version is regarded as the definitive version.
