HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
3582Add text/ping registration.2009-08-11 05:57
@@ -62026,22 +62026,22 @@ interface <dfn>SQLTransactionSync</dfn> {
   <p>User agents should allow the user to adjust this behavior, for
   example in conjunction with a setting that disables the sending of
   HTTP <code title="http-referer">Referer</code> (sic) headers. Based
   on the user's preferences, UAs may either <span>ignore</span> the
   <code title="attr-hyperlink-ping">ping</code> attribute altogether,
   or selectively ignore URLs in the list (e.g. ignoring any
   third-party URLs).</p>
 
   <p>For URLs that are HTTP URLs, the requests must be performed by
   <span title="fetch">fetching</span> the specified URLs using the
-  POST method, with an entity body with the <span>MIME type</span> <code
-  title="">text/ping</code> consisting of the four-character string
+  POST method, with an entity body with the <span>MIME type</span>
+  <code>text/ping</code> consisting of the four-character string
   "<code title="">PING</code>". All relevant cookie and HTTP
   authentication headers must be included in the request. Which other
   headers are required depends on the URLs involved.</p>
 
   <dl class="switch">
 
    <dt>If both the <span title="the document's address">address</span>
    of the <code>Document</code> object containing the hyperlink being
    audited and the ping URL have the <span>same origin</span></dt>
 
@@ -86115,20 +86115,86 @@ interface <span>HTMLDocument</span> {
    <dt>Author:</dt>
    <dd>Ian Hickson &lt;ian@hixie.ch></dd>
    <dt>Change controller:</dt>
    <dd>W3C and WHATWG</dd>
   </dl>
 
   <p>Fragment identifiers have no meaning with
   <code>text/cache-manifest</code> resources.</p>
 
 
+  <h3><dfn><code>text/ping</code></dfn></h3>
+
+  <!--
+   To: ietf-types@iana.org
+   Subject: Registration of media type text/ping
+  -->
+
+  <dl>
+   <dt>Type name:</dt>
+   <dd>text</dd>
+   <dt>Subtype name:</dt>
+   <dd>ping</dd>
+   <dt>Required parameters:</dt>
+   <dd>No parameters</dd>
+   <dt>Optional parameters:</dt>
+   <dd>No parameters</dd>
+   <dt>Encoding considerations:</dt>
+   <dd>Not applicable.</dd>
+   <dt>Security considerations:</dt>
+   <dd>
+    <p>If used exclusively in the fashion described in the context of
+    <span>hyperlink auditing</span>, this type introduces no new
+    security concerns.</p>
+   </dd>
+   <dt>Interoperability considerations:</dt>
+   <dd>
+    Rules applicable to this type are defined in this specification.
+   </dd>
+   <dt>Published specification:</dt>
+   <dd>
+    This document is the relevant specification.
+   </dd>
+   <dt>Applications that use this media type:</dt>
+   <dd>
+    Web browsers.
+   </dd>
+   <dt>Additional information:</dt>
+   <dd>
+    <dl>
+     <dt>Magic number(s):</dt>
+     <dd><code>text/ping</code> resources always consist of the four
+     bytes 0x50 0x49 0x4E 0x47 (ASCII "PING").</dd>
+     <dt>File extension(s):</dt>
+     <dd>No specific file extension is recommended for this type.</dd>
+     <dt>Macintosh file type code(s):</dt>
+     <dd>No specific Macintosh file type codes are recommended for this type.</dd>
+    </dl>
+   </dd>
+   <dt>Person &amp; email address to contact for further information:</dt>
+   <dd>Ian Hickson &lt;ian@hixie.ch></dd>
+   <dt>Intended usage:</dt>
+   <dd>Common</dd>
+   <dt>Restrictions on usage:</dt>
+   <dd>Only intended for use with HTTP POST requests generated as part
+   of a Web browser's processing of the <code
+   title="attr-hyperlink-ping">ping</code> attribute.</dd>
+   <dt>Author:</dt>
+   <dd>Ian Hickson &lt;ian@hixie.ch></dd>
+   <dt>Change controller:</dt>
+   <dd>W3C and WHATWG</dd>
+  </dl>
+
+  <p>Fragment identifiers have no meaning with
+  <code>text/ping</code> resources.</p>
+
+
   <h3><dfn><code>application/microdata+json</code></dfn></h3>
 
   <!--
    To: ietf-types@iana.org
    Subject: Registration of media type application/microdata+json
   -->
 
   <dl>
    <dt>Type name:</dt>
    <dd>application</dd>

|