Changeset 1791 for draft-ietf-httpbis

Timestamp:

15/07/12 15:46:37 (8 years ago)

Author:

julian.reschke@…

Message:

fix reference target

Location:

draft-ietf-httpbis/latest

Files:

• p7-auth.html (modified) (5 diffs)
• p7-auth.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p7-auth.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires January 15, 2013"; 
+       content: "Expires January 16, 2013"; 
   } 
   @bottom-right {
@@ -489 +489 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-07-15">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework.">
@@ -520 +520 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 15, 2013</td>
+               <td class="left">Expires: January 16, 2013</td>
                <td class="right">greenbytes</td>
             </tr>
             <tr>
                <td class="left"></td>
-               <td class="right">July 14, 2012</td>
+               <td class="right">July 15, 2012</td>
             </tr>
          </tbody>
@@ -552 +552 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on January 15, 2013.</p>
+      <p>This Internet-Draft will expire on January 16, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1012 +1012 @@
          authentication credentials for other resources.
       </p>
-      <p id="rfc.section.6.2.p.2">This is of particular concern when a server hosts resources for multiple parties under the same canonical root URI (<a href="#protection.spaces" title="Protection Spaces">Section&nbsp;6.2</a>). Possible mitigation strategies include restricting direct access to authentication credentials (i.e., not making the content
+      <p id="rfc.section.6.2.p.2">This is of particular concern when a server hosts resources for multiple parties under the same canonical root URI (<a href="#protection.space" title="Protection Space (Realm)">Section&nbsp;2.2</a>). Possible mitigation strategies include restricting direct access to authentication credentials (i.e., not making the content
          of the <a href="#header.authorization" class="smpl">Authorization</a> request header field available), and separating protection spaces by using a different host name for each party.
       </p>

draft-ietf-httpbis/latest/p7-auth.xml

@@ -840 +840 @@
 <t>
   This is of particular concern when a server hosts resources for multiple
-  parties under the same canonical root URI (<xref target="protection.spaces"/>).
+  parties under the same canonical root URI (<xref target="protection.space"/>).
   Possible mitigation strategies include restricting direct access to
   authentication credentials (i.e., not making the content of the