1 = Free/Busy Publishing = 2 3 Although iTIP [[http://tools.ietf.org/html/rfc5546#section-3.3|specifies]] the exchange 4 of free/busy information through requests and replies, many mail-based calendar clients 5 do not support these particular operations over e-mail when providing general 6 [[http://tools.ietf.org/html/rfc6047|iMIP]] support. However, they may support the 7 acquisition of free/busy information over HTTP. 8 9 The publishing of free/busy resources for users can be enabled by default in the 10 [[../Configuration|configuration]] by changing the `PUBLISHING_DEFAULT` setting: 11 12 {{{ 13 PUBLISHING_DEFAULT = "publish" 14 }}} 15 16 For this setting to have an effect, the `SHARING_DEFAULT` setting will need to be 17 changed to enable free/busy sharing by default: 18 19 {{{ 20 SHARING_DEFAULT = "share" 21 }}} 22 23 Users can enable sharing and publishing themselves by accessing their profile in the 24 [[../CalendarManager|management interface]]. 25 26 Depending on the [[../WebServerIntegration|Web server configuration]], resources are 27 made available at a location resembling the following: 28 29 {{{ 30 https://webserver.example.com/freebusy/ 31 }}} 32 33 Individual user data is published in locations like this: 34 35 {{{ 36 https://webserver.example.com/freebusy/mailto%3Avincent.vole%40example.com/freebusy 37 }}} 38 39 Here, the `mailto:vincent.vole@example.com` identity has been URL-encoded. Web 40 browsers and mail programs may perform such encoding on a location given more 41 informally as follows: 42 43 {{{ 44 https://webserver.example.com/freebusy/mailto:vincent.vole@example.com/freebusy 45 }}} 46 47 However, the properly-encoded version is regarded as the definitive version.