<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to ServiceDiscovery</title><link>https://sourceforge.net/p/coils/wiki/ServiceDiscovery/</link><description>Recent changes to ServiceDiscovery</description><atom:link href="https://sourceforge.net/p/coils/wiki/ServiceDiscovery/feed" rel="self"/><language>en</language><lastBuildDate>Sun, 25 Nov 2012 22:33:40 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/coils/wiki/ServiceDiscovery/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage ServiceDiscovery modified by Adam Tauno Williams</title><link>https://sourceforge.net/p/coils/wiki/ServiceDiscovery/</link><description>&lt;pre&gt;--- v1
+++ v2
@@ -1,4 +1,6 @@
 One problem that faces all WebDAV clients is where to find the root of the WebDAV hierarchy.  Often clients *assume* that this will be the root resource, but this is frequently not true and presents problems for _hosted_ servers which may be beneath another authorities root.  
+
+Support for ___.well_knwon___ URLs is implemented as of r4364 (121015c9a905) pre-0.1.49.
 
 **RFC6785 Well Knowns**
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Adam Tauno Williams</dc:creator><pubDate>Sun, 25 Nov 2012 22:33:40 -0000</pubDate><guid>https://sourceforge.net148e940f301dad6289e07b16a19be8b9890fc87d</guid></item><item><title>WikiPage ServiceDiscovery modified by Adam Tauno Williams</title><link>https://sourceforge.net/p/coils/wiki/ServiceDiscovery/</link><description>One problem that faces all WebDAV clients is where to find the root of the WebDAV hierarchy.  Often clients *assume* that this will be the root resource, but this is frequently not true and presents problems for _hosted_ servers which may be beneath another authorities root.  

**RFC6785 Well Knowns**

The solution proposed by [RFC5785](http://tools.ietf.org/rfc/rfc5785.txt) is the use of the .well_known/_resource_ URL to discover the root of the resource tree.  This is in keeping with the customary UNIX tradition that resources whose name begins with a dot are _hidden_.  The value of _resource_ is not defined by the RFC; but a convention of *caldav* and *carddav* is used, at least by iOS devices.

URL                   | Resource
----------------------|--------------------
.well_known/caldav    | CALDAV resources
.well_known/carddav   | CardDAV resources

These URLs should perform a 301 HTTP redirect to the real location of the resources if they are present elsewhere.

**Service Discovery via DNS**

SRV and TXT records can also be used by clients to discover the location or resources.  For example the following DNS records indicate the location of CardDAV and CALDAV services over SSL.

DNS Records |
---------------------------------------------------------|
_carddavs._tcp 86400 IN SRV 10 20 443 coils.example.org. |
_carddavs._tcp 86400 IN TXT dav=/dav |
_caldavs._tcp 86400 IN SRV 10 20 443 coils.example.org.|
_caldavs._tcp 86400 IN TXT dav=/dav |
 </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Adam Tauno Williams</dc:creator><pubDate>Thu, 08 Nov 2012 19:30:31 -0000</pubDate><guid>https://sourceforge.net387d1fce7c6150cdf6a7a677950ba7e55c50836e</guid></item></channel></rss>