Ignore:
Timestamp:
Jul 15, 2012, 8:46:37 AM (7 years ago)
Author:
julian.reschke@…
Message:

fix reference target

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p7-auth.html

    r1773 r1791  
    449449  }
    450450  @bottom-center {
    451        content: "Expires January 15, 2013";
     451       content: "Expires January 16, 2013";
    452452  }
    453453  @bottom-right {
     
    489489      <meta name="dct.creator" content="Reschke, J. F.">
    490490      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    491       <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
     491      <meta name="dct.issued" scheme="ISO8601" content="2012-07-15">
    492492      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    493493      <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.">
     
    520520            </tr>
    521521            <tr>
    522                <td class="left">Expires: January 15, 2013</td>
     522               <td class="left">Expires: January 16, 2013</td>
    523523               <td class="right">greenbytes</td>
    524524            </tr>
    525525            <tr>
    526526               <td class="left"></td>
    527                <td class="right">July 14, 2012</td>
     527               <td class="right">July 15, 2012</td>
    528528            </tr>
    529529         </tbody>
     
    552552         in progress”.
    553553      </p>
    554       <p>This Internet-Draft will expire on January 15, 2013.</p>
     554      <p>This Internet-Draft will expire on January 16, 2013.</p>
    555555      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    556556      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    10121012         authentication credentials for other resources.
    10131013      </p>
    1014       <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
     1014      <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
    10151015         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.
    10161016      </p>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r1773 r1791  
    840840<t>
    841841  This is of particular concern when a server hosts resources for multiple
    842   parties under the same canonical root URI (<xref target="protection.spaces"/>).
     842  parties under the same canonical root URI (<xref target="protection.space"/>).
    843843  Possible mitigation strategies include restricting direct access to
    844844  authentication credentials (i.e., not making the content of the
Note: See TracChangeset for help on using the changeset viewer.