Changeset 1791 for draft-ietf-httpbis
- Timestamp:
- 15/07/12 15:46:37 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p7-auth.html
r1773 r1791 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 5, 2013";451 content: "Expires January 16, 2013"; 452 452 } 453 453 @bottom-right { … … 489 489 <meta name="dct.creator" content="Reschke, J. F."> 490 490 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 491 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 4">491 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 492 492 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 493 493 <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 "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework."> … … 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: January 1 5, 2013</td>522 <td class="left">Expires: January 16, 2013</td> 523 523 <td class="right">greenbytes</td> 524 524 </tr> 525 525 <tr> 526 526 <td class="left"></td> 527 <td class="right">July 1 4, 2012</td>527 <td class="right">July 15, 2012</td> 528 528 </tr> 529 529 </tbody> … … 552 552 in progress”. 553 553 </p> 554 <p>This Internet-Draft will expire on January 1 5, 2013.</p>554 <p>This Internet-Draft will expire on January 16, 2013.</p> 555 555 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 556 556 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1012 1012 authentication credentials for other resources. 1013 1013 </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.space s" title="Protection Spaces">Section 6.2</a>). Possible mitigation strategies include restricting direct access to authentication credentials (i.e., not making the content1014 <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 2.2</a>). Possible mitigation strategies include restricting direct access to authentication credentials (i.e., not making the content 1015 1015 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. 1016 1016 </p> -
draft-ietf-httpbis/latest/p7-auth.xml
r1773 r1791 840 840 <t> 841 841 This is of particular concern when a server hosts resources for multiple 842 parties under the same canonical root URI (<xref target="protection.space s"/>).842 parties under the same canonical root URI (<xref target="protection.space"/>). 843 843 Possible mitigation strategies include restricting direct access to 844 844 authentication credentials (i.e., not making the content of the
Note: See TracChangeset
for help on using the changeset viewer.