Ignore:
Timestamp:
18/11/13 21:32:31 (7 years ago)
Author:
julian.reschke@…
Message:

tiny rephrasing (see #522)

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

Legend:

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

    r2495 r2500  
    445445  }
    446446  @bottom-center {
    447        content: "Expires May 19, 2014";
     447       content: "Expires May 22, 2014";
    448448  }
    449449  @bottom-right {
     
    480480      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    481481      <link href="p6-cache.html" rel="prev">
    482       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.607, 2013/10/15 13:23:22, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     482      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.608, 2013/11/05 01:54:09, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    483483      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    484484      <meta name="dct.creator" content="Fielding, R.">
    485485      <meta name="dct.creator" content="Reschke, J. F.">
    486486      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    487       <meta name="dct.issued" scheme="ISO8601" content="2013-11-15">
     487      <meta name="dct.issued" scheme="ISO8601" content="2013-11-18">
    488488      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    489489      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.">
     
    513513            <tr>
    514514               <td class="left">Intended status: Standards Track</td>
    515                <td class="right">November 15, 2013</td>
     515               <td class="right">November 18, 2013</td>
    516516            </tr>
    517517            <tr>
    518                <td class="left">Expires: May 19, 2014</td>
     518               <td class="left">Expires: May 22, 2014</td>
    519519               <td class="right"></td>
    520520            </tr>
     
    543543            in progress”.
    544544         </p>
    545          <p>This Internet-Draft will expire on May 19, 2014.</p>
     545         <p>This Internet-Draft will expire on May 22, 2014.</p>
    546546      </div>
    547547      <div id="rfc.copyrightnotice">
     
    762762               its request to the responding proxy. If that recipient is also a proxy, it will generally consume the Proxy-Authenticate header
    763763               field (and generate an appropriate <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a> in a subsequent request) rather than forward the header field to its own outbound clients. However, if a recipient proxy needs
    764                to obtain its own credentials by requesting them from a further outbound client, it will generate its own 407 response, which
    765                might have the appearance of forwarding the Proxy-Authenticate header field if both proxies use the same challenge set.
     764               to obtain its own credentials by requesting them from a further outbound client, it will generate its own 407 response, and
     765               this might have the appearance of forwarding the Proxy-Authenticate header field if both proxies use the same challenge set.
    766766            </p>
    767767            <p id="rfc.section.4.2.p.4">Note that the parsing considerations for <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> apply to this header field as well; see <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.2" title="WWW-Authenticate">Section&nbsp;4.4</a> for details.
     
    11651165         <div id="changes.since.25">
    11661166            <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;<a href="#changes.since.25">Since draft-ietf-httpbis-p7-auth-25</a></h2>
    1167             <p id="rfc.section.D.2.p.1">None yet.</p>
     1167            <p id="rfc.section.D.2.p.1">Closed issues: </p>
     1168            <ul>
     1169               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/522">http://tools.ietf.org/wg/httpbis/trac/ticket/522</a>&gt;: "Gen-art review of draft-ietf-httpbis-p7-auth-25"
     1170               </li>
     1171            </ul>
    11681172         </div>
    11691173      </div>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r2495 r2500  
    396396   However, if a recipient proxy needs to obtain its own credentials by
    397397   requesting them from a further outbound client, it will generate its own
    398    407 response, which might have the appearance of forwarding the
     398   407 response, and this might have the appearance of forwarding the
    399399   Proxy-Authenticate header field if both proxies use the same challenge set.
    400400</t>
     
    11091109<section title="Since draft-ietf-httpbis-p7-auth-25" anchor="changes.since.25">
    11101110<t>
    1111   None yet.
     1111  Closed issues:
     1112  <list style="symbols">
     1113    <t>
     1114      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/522"/>:
     1115      "Gen-art review of draft-ietf-httpbis-p7-auth-25"
     1116    </t>
     1117  </list>
    11121118</t>
    11131119</section>
Note: See TracChangeset for help on using the changeset viewer.