Search results
From Davical
Jump to navigationJump to search
- * [[Fr:RFC Compliance|Respect des RFC]] ...2 KB (242 words) - 22:57, 21 January 2016
- ...esponses to requests for 'well-known' URLs as defined in {{Well-known URLs RFC}} ...738 bytes (94 words) - 19:27, 15 September 2015
- ...ren. Brukt for automatisk konfigurasjon i noen klienter. {{Well-known URLs RFC}} ...732 bytes (94 words) - 19:26, 15 September 2015
- ...tes aux requètes 'well-known' URLs définis par '''(en)'''{{Well-known URLs RFC}}. ...761 bytes (102 words) - 19:33, 15 September 2015
- * [[RFC Compliance]] ...2 KB (159 words) - 22:54, 4 October 2022
- ...esponses to requests for 'well-known' URLs as defined in {{Well-known URLs RFC}} ...2 KB (240 words) - 04:03, 22 November 2018
- ...owever, and are the default in davical up to now. How to be complient with RFC and make Apple client to work? ...3 KB (411 words) - 21:13, 30 April 2014
- Furthermore, {{CalDAV Scheduling RFC}} adds several further CalDAV permissions: Two more aggregate permissions are also added with this RFC: ...9 KB (1,264 words) - 14:02, 12 June 2017
- ...an employee working on a validation library for CalDAV data, to allow non-RFC compliant legacy data in tables to be fixed. ...2 KB (350 words) - 00:04, 30 June 2015
- {{Languages|RFC Compliance/WebDAV Tickets}} ...11 KB (1,331 words) - 11:07, 7 January 2018
