- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Wed, 17 Apr 2013 09:52:32 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv29379/drafts
Modified Files:
tracking-dnt.html
Log Message:
Include the trailing slash in the well-known location to make it easier to implement DNT in sites with delegated namespaces (i.e., access control by directory); also, read my own spec and use the correct URI Template syntax
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2013/04/14 01:36:47 1.197
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2013/04/17 09:52:32 1.198
@@ -825,7 +825,7 @@
An origin server MUST provide a <dfn>site-wide tracking status
resource</dfn> at the well-known identifier [[RFC5785]]
</p>
- <pre>/.well-known/dnt</pre>
+ <pre>/.well-known/dnt/</pre>
<p>
(relative to the URI of that origin server) for obtaining
information about the potential tracking behavior of resources
@@ -863,7 +863,7 @@
The <dfn>tracking status resource space</dfn> is defined by the
following URI Template [[URI-TEMPLATE]]:
</p>
- <pre>/.well-known/dnt{/status-id}</pre>
+ <pre>/.well-known/dnt/{+status-id}</pre>
<p>
where the value of <code>status-id</code> is a string of URI-safe
characters provided by a <a>Tk</a> field-value in response to a
@@ -1287,7 +1287,7 @@
<p>
Deployment of this protocol for a given service can
be discovered by making a retrieval request on the site-wide
- tracking resource <q><code>/.well-known/dnt</code></q> relative
+ tracking resource <q><code>/.well-known/dnt/</code></q> relative
to the service URI.
</p>
<p>
Received on Wednesday, 17 April 2013 09:52:33 UTC