Ignore:
Timestamp:
14/06/14 11:20:37 (6 years ago)
Author:
julian.reschke@…
Message:

update to latest version of rfc2629.xslt, regen all HTML

File:
1 edited

Legend:

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

    r1099 r2726  
    22  PUBLIC "-//W3C//DTD HTML 4.01//EN">
    33<html lang="en">
    4    <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
     4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    66      <title>HTTP/1.1, part 7: Authentication</title><style type="text/css" title="Xml2Rfc (sans serif)">
     
    2424body {
    2525  color: black;
    26   font-family: verdana, helvetica, arial, sans-serif;
    27   font-size: 10pt;
     26  font-family: cambria, helvetica, arial, sans-serif;
     27  font-size: 11pt;
     28  margin-right: 2em;
    2829}
    2930cite {
    3031  font-style: normal;
    3132}
    32 dd {
    33   margin-right: 2em;
    34 }
    3533dl {
    3634  margin-left: 2em;
    3735}
    38 
    3936ul.empty {
    4037  list-style-type: none;
     
    5047}
    5148h1 {
    52   font-size: 14pt;
     49  font-size: 130%;
    5350  line-height: 21pt;
    5451  page-break-after: avoid;
     
    5754  page-break-before: always;
    5855}
    59 h1 a {
    60   color: #333333;
    61 }
    6256h2 {
    63   font-size: 12pt;
     57  font-size: 120%;
    6458  line-height: 15pt;
    6559  page-break-after: avoid;
    6660}
    67 h3, h4, h5, h6 {
    68   font-size: 10pt;
     61h3 {
     62  font-size: 110%;
    6963  page-break-after: avoid;
    7064}
    71 h2 a, h3 a, h4 a, h5 a, h6 a {
     65h4, h5, h6 {
     66  page-break-after: avoid;
     67}
     68h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    7269  color: black;
    7370}
     
    7774li {
    7875  margin-left: 2em;
    79   margin-right: 2em;
    8076}
    8177ol {
    8278  margin-left: 2em;
    83   margin-right: 2em;
     79}
     80ol.la {
     81  list-style-type: lower-alpha;
     82}
     83ol.ua {
     84  list-style-type: upper-alpha;
    8485}
    8586ol p {
     
    8889p {
    8990  margin-left: 2em;
    90   margin-right: 2em;
    9191}
    9292pre {
     
    9494  background-color: lightyellow;
    9595  padding: .25em;
     96  page-break-inside: avoid;
    9697}
    9798pre.text2 {
     
    123124  border-spacing: 1px;
    124125  width: 95%;
    125   font-size: 10pt;
     126  font-size: 11pt;
    126127  color: white;
    127128}
     
    131132td.topnowrap {
    132133  vertical-align: top;
    133   white-space: nowrap; 
     134  white-space: nowrap;
    134135}
    135136table.header td {
     
    151152  list-style: none;
    152153  margin-left: 1.5em;
    153   margin-right: 0em;
    154154  padding-left: 0em;
    155155}
     
    157157  line-height: 150%;
    158158  font-weight: bold;
    159   font-size: 10pt;
    160159  margin-left: 0em;
    161   margin-right: 0em;
    162160}
    163161ul.toc li li {
    164162  line-height: normal;
    165163  font-weight: normal;
    166   font-size: 9pt;
     164  font-size: 10pt;
    167165  margin-left: 0em;
    168   margin-right: 0em;
    169166}
    170167li.excluded {
     
    173170ul p {
    174171  margin-left: 0em;
     172}
     173.title, .filename, h1, h2, h3, h4 {
     174  font-family: candara, helvetica, arial, sans-serif;
     175}
     176samp, tt, code, pre {
     177  font: consolas, monospace;
    175178}
    176179ul.ind, ul.ind ul {
    177180  list-style: none;
    178181  margin-left: 1.5em;
    179   margin-right: 0em;
    180182  padding-left: 0em;
    181183  page-break-before: avoid;
     
    185187  line-height: 200%;
    186188  margin-left: 0em;
    187   margin-right: 0em;
    188189}
    189190ul.ind li li {
     
    191192  line-height: 150%;
    192193  margin-left: 0em;
    193   margin-right: 0em;
    194194}
    195195.avoidbreak {
     
    215215  font-weight: bold;
    216216  text-align: center;
    217   font-size: 9pt;
     217  font-size: 10pt;
    218218}
    219219.filename {
    220220  color: #333333;
     221  font-size: 75%;
    221222  font-weight: bold;
    222   font-size: 12pt;
    223223  line-height: 21pt;
    224224  text-align: center;
     
    227227  font-weight: bold;
    228228}
    229 .hidden {
    230   display: none;
    231 }
    232229.left {
    233230  text-align: left;
     
    237234}
    238235.title {
    239   color: #990000;
    240   font-size: 18pt;
     236  color: green;
     237  font-size: 150%;
    241238  line-height: 18pt;
    242239  font-weight: bold;
     
    244241  margin-top: 36pt;
    245242}
    246 .vcardline {
    247   display: block;
    248 }
    249243.warning {
    250   font-size: 14pt;
     244  font-size: 130%;
    251245  background-color: yellow;
    252246}
     
    257251    display: none;
    258252  }
    259  
     253
    260254  a {
    261255    color: black;
     
    272266    background-color: white;
    273267    vertical-align: top;
    274     font-size: 12pt;
    275   }
    276 
    277   ul.toc a::after {
     268    font-size: 110%;
     269  }
     270
     271  ul.toc a:nth-child(2)::after {
    278272    content: leader('.') target-counter(attr(href), page);
    279273  }
    280  
     274
    281275  ul.ind li li a {
    282276    content: target-counter(attr(href), page);
    283277  }
    284  
     278
    285279  .print2col {
    286280    column-count: 2;
     
    292286@page {
    293287  @top-left {
    294        content: "Internet-Draft"; 
    295   } 
     288       content: "Internet-Draft";
     289  }
    296290  @top-right {
    297        content: "December 2007"; 
    298   } 
     291       content: "December 2007";
     292  }
    299293  @top-center {
    300        content: "HTTP/1.1"; 
    301   } 
     294       content: "HTTP/1.1";
     295  }
    302296  @bottom-left {
    303        content: "Fielding, et al."; 
    304   } 
     297       content: "Fielding, et al.";
     298  }
    305299  @bottom-center {
    306        content: "Standards Track";
    307   } 
     300       content: "Expires June 22, 2008";
     301  }
    308302  @bottom-right {
    309        content: "[Page " counter(page) "]"; 
    310   } 
    311 }
    312 
    313 @page:first { 
     303       content: "[Page " counter(page) "]";
     304  }
     305}
     306
     307@page:first {
    314308    @top-left {
    315309      content: normal;
     
    333327      <link rel="Chapter" title="6 Acknowledgments" href="#rfc.section.6">
    334328      <link rel="Chapter" href="#rfc.section.7" title="7 References">
    335       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.537, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     329      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    336330      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    337331      <meta name="dct.creator" content="Fielding, R.">
     
    361355            </tr>
    362356            <tr>
    363                <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>, <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     357               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2068">2068</a>, <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    364358               </td>
    365359               <td class="right">J. Gettys</td>
    366360            </tr>
    367361            <tr>
    368                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)
     362               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2617">2617</a> (if approved)
    369363               </td>
    370364               <td class="right">One Laptop per Child</td>
     
    417411      </table>
    418412      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-00</span></p>
    419       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    420       <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
    421          is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
    422          6 of BCP 79.
    423       </p>
    424       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
    425          that other groups may also distribute working documents as Internet-Drafts.
    426       </p>
    427       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    428          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    429          in progress”.
    430       </p>
    431       <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
    432       </p>
    433       <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
    434       </p>
    435       <p>This Internet-Draft will expire on June 22, 2008.</p>
    436       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     413      <div id="rfc.status">
     414         <h1><a href="#rfc.status">Status of this Memo</a></h1>
     415         <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
     416            is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
     417            6 of BCP 79.
     418         </p>
     419         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
     420            that other groups may also distribute working documents as Internet-Drafts.
     421         </p>
     422         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     423            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     424            in progress”.
     425         </p>
     426         <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
     427         </p>
     428         <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
     429         </p>
     430         <p>This Internet-Draft will expire on June 22, 2008.</p>
     431      </div>
     432      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    437433      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    438434         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
    439435         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
    440436         7 defines HTTP Authentication.
    441       </p> 
    442       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     437      </p>
     438      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    443439      <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
    444440         mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
     
    447443         to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
    448444         after draft 00 is submitted.
    449       </p> 
     445      </p>
    450446      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    451447         list is at &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/report/11">http://www3.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/">http://www3.tools.ietf.org/wg/httpbis/</a>&gt;.
    452       </p> 
     448      </p>
    453449      <hr class="noprint">
    454450      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    455451      <ul class="toc">
    456          <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
    457          <li>2.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Status Code Definitions</a><ul>
    458                <li>2.1&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
    459                <li>2.2&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
     452         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
     453         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Status Code Definitions</a><ul>
     454               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
     455               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
    460456            </ul>
    461457         </li>
    462          <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
    463                <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
    464                <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
    465                <li>3.3&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
    466                <li>3.4&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
     458         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     459               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
     460               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
     461               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
     462               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
    467463            </ul>
    468464         </li>
    469          <li>4.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
    470          <li>5.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
    471                <li>5.1&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
     465         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
     466         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     467               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
    472468            </ul>
    473469         </li>
    474          <li>6.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    475          <li>7.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
     470         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     471         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
     472         <li><a href="#rfc.index">Index</a></li>
    476473         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    477          <li><a href="#rfc.index">Index</a></li>
    478474         <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    479475      </ul>
    480       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    481       <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to access control and authentication. Right now it only includes the extracted
    482          relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">[RFC2616]</cite> with only minor edits.
    483       </p>
    484       <p id="rfc.section.1.p.2">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-response authentication mechanisms which can be used by a server to challenge a client request and by a client to
    485          provide authentication information. The general framework for access authentication, and the specification of "basic" and
    486          "digest" authentication, are specified in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. This specification adopts the definitions of "challenge" and "credentials" from that specification.
    487       </p>
    488       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Status Code Definitions
    489       </h1>
    490       <div id="rfc.iref."></div>
    491       <div id="rfc.iref.s.1"></div>
    492       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h2>
    493       <p id="rfc.section.2.1.p.1">The request requires user authentication. The response <em class="bcp14">MUST</em> include a WWW-Authenticate header field (<a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.1" title="WWW-Authenticate">Section&nbsp;3.4</a>) containing a challenge applicable to the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Authorization header field (<a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section&nbsp;3.1</a>). If the request already included Authorization credentials, then the 401 response indicates that authorization has been
    494          refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
    495          already attempted authentication at least once, then the user <em class="bcp14">SHOULD</em> be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP
    496          access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.2"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
    497       </p>
    498       <div id="rfc.iref.1"></div>
    499       <div id="rfc.iref.s.2"></div>
    500       <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h2>
    501       <p id="rfc.section.2.2.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The
    502          proxy <em class="bcp14">MUST</em> return a Proxy-Authenticate header field (<a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.1" title="Proxy-Authenticate">Section&nbsp;3.2</a>) containing a challenge applicable to the proxy for the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Proxy-Authorization header field (<a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.1" title="Proxy-Authorization">Section&nbsp;3.3</a>). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
    503       </p>
    504       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
    505       <p id="rfc.section.3.p.1">This section defines the syntax and semantics of all standard HTTP/1.1 header fields. For entity-header fields, both sender
    506          and recipient refer to either the client or the server, depending on who sends and who receives the entity.
    507       </p>
    508       <div id="rfc.iref.a.1"></div>
    509       <div id="rfc.iref.h.1"></div>
    510       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.authorization" href="#header.authorization">Authorization</a></h2>
    511       <p id="rfc.section.3.1.p.1">A user agent that wishes to authenticate itself with a server-- usually, but not necessarily, after receiving a 401 response--does
    512          so by including an Authorization request-header field with the request. The Authorization field value consists of credentials
    513          containing the authentication information of the user agent for the realm of the resource being requested.
    514       </p>
    515       <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>       Authorization  = "Authorization" ":" credentials
     476      <div id="introduction">
     477         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     478         <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to access control and authentication. Right now it only includes the extracted
     479            relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">[RFC2616]</cite> with only minor edits.
     480         </p>
     481         <p id="rfc.section.1.p.2">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-response authentication mechanisms which can be used by a server to challenge a client request and by a client to
     482            provide authentication information. The general framework for access authentication, and the specification of "basic" and
     483            "digest" authentication, are specified in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. This specification adopts the definitions of "challenge" and "credentials" from that specification.
     484         </p>
     485      </div>
     486      <div>
     487         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Status Code Definitions
     488         </h1>
     489         <div id="status.401">
     490            <div id="rfc.iref.4.1"></div>
     491            <div id="rfc.iref.s.1"></div>
     492            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#status.401">401 Unauthorized</a></h2>
     493            <p id="rfc.section.2.1.p.1">The request requires user authentication. The response <em class="bcp14">MUST</em> include a WWW-Authenticate header field (<a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.1" title="WWW-Authenticate">Section&nbsp;3.4</a>) containing a challenge applicable to the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Authorization header field (<a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section&nbsp;3.1</a>). If the request already included Authorization credentials, then the 401 response indicates that authorization has been
     494               refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
     495               already attempted authentication at least once, then the user <em class="bcp14">SHOULD</em> be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP
     496               access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.2"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
     497            </p>
     498         </div>
     499         <div id="status.407">
     500            <div id="rfc.iref.4.2"></div>
     501            <div id="rfc.iref.s.2"></div>
     502            <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></h2>
     503            <p id="rfc.section.2.2.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The
     504               proxy <em class="bcp14">MUST</em> return a Proxy-Authenticate header field (<a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.1" title="Proxy-Authenticate">Section&nbsp;3.2</a>) containing a challenge applicable to the proxy for the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Proxy-Authorization header field (<a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.1" title="Proxy-Authorization">Section&nbsp;3.3</a>). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
     505            </p>
     506         </div>
     507      </div>
     508      <div id="header.fields">
     509         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     510         <p id="rfc.section.3.p.1">This section defines the syntax and semantics of all standard HTTP/1.1 header fields. For entity-header fields, both sender
     511            and recipient refer to either the client or the server, depending on who sends and who receives the entity.
     512         </p>
     513         <div id="header.authorization">
     514            <div id="rfc.iref.a.1"></div>
     515            <div id="rfc.iref.h.1"></div>
     516            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.authorization">Authorization</a></h2>
     517            <p id="rfc.section.3.1.p.1">A user agent that wishes to authenticate itself with a server-- usually, but not necessarily, after receiving a 401 response--does
     518               so by including an Authorization request-header field with the request. The Authorization field value consists of credentials
     519               containing the authentication information of the user agent for the realm of the resource being requested.
     520            </p>
     521            <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>       Authorization  = "Authorization" ":" credentials
    516522</pre><p id="rfc.section.3.1.p.3">HTTP access authentication is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. If a request is authenticated and a realm specified, the same credentials <em class="bcp14">SHOULD</em> be valid for all other requests within this realm (assuming that the authentication scheme itself does not require otherwise,
    517          such as credentials that vary according to a challenge value or using synchronized clocks).
    518       </p>
    519       <p id="rfc.section.3.1.p.4">When a shared cache (see <a href="p6-cache.html#shared.and.non-shared.caches" title="Shared and Non-Shared Caches">Section 2.7</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) receives a request containing an Authorization field, it <em class="bcp14">MUST NOT</em> return the corresponding response as a reply to any other request, unless one of the following specific exceptions holds:
    520       </p>
    521       <p id="rfc.section.3.1.p.5"> </p>
    522       <ol>
    523          <li>If the response includes the "s-maxage" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But (if the specified maximum age has passed) a proxy cache <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
    524             the new request. (This is the defined behavior for s-maxage.) If the response includes "s-maxage=0", the proxy <em class="bcp14">MUST</em> always revalidate it before re-using it.
    525          </li>
    526          <li>If the response includes the "must-revalidate" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But if the response is stale, all caches <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
    527             the new request.
    528          </li>
    529          <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
    530          </li>
    531       </ol>
    532       <div id="rfc.iref.p.1"></div>
    533       <div id="rfc.iref.h.2"></div>
    534       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.proxy-authenticate" href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
    535       <p id="rfc.section.3.2.p.1">The Proxy-Authenticate response-header field <em class="bcp14">MUST</em> be included as part of a 407 (Proxy Authentication Required) response. The field value consists of a challenge that indicates
    536          the authentication scheme and parameters applicable to the proxy for this Request-URI.
    537       </p>
    538       <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.2"></span>    Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
     523               such as credentials that vary according to a challenge value or using synchronized clocks).
     524            </p>
     525            <p id="rfc.section.3.1.p.4">When a shared cache (see <a href="p6-cache.html#shared.and.non-shared.caches" title="Shared and Non-Shared Caches">Section 2.7</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) receives a request containing an Authorization field, it <em class="bcp14">MUST NOT</em> return the corresponding response as a reply to any other request, unless one of the following specific exceptions holds:
     526            </p>
     527            <p id="rfc.section.3.1.p.5"></p>
     528            <ol>
     529               <li>If the response includes the "s-maxage" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But (if the specified maximum age has passed) a proxy cache <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
     530                  the new request. (This is the defined behavior for s-maxage.) If the response includes "s-maxage=0", the proxy <em class="bcp14">MUST</em> always revalidate it before re-using it.
     531               </li>
     532               <li>If the response includes the "must-revalidate" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But if the response is stale, all caches <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
     533                  the new request.
     534               </li>
     535               <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
     536               </li>
     537            </ol>
     538         </div>
     539         <div id="header.proxy-authenticate">
     540            <div id="rfc.iref.p.1"></div>
     541            <div id="rfc.iref.h.2"></div>
     542            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
     543            <p id="rfc.section.3.2.p.1">The Proxy-Authenticate response-header field <em class="bcp14">MUST</em> be included as part of a 407 (Proxy Authentication Required) response. The field value consists of a challenge that indicates
     544               the authentication scheme and parameters applicable to the proxy for this Request-URI.
     545            </p>
     546            <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.2"></span>    Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
    539547</pre><p id="rfc.section.3.2.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.5"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. Unlike WWW-Authenticate, the Proxy-Authenticate header field applies only to the current connection and <em class="bcp14">SHOULD NOT</em> be passed on to downstream clients. However, an intermediate proxy might need to obtain its own credentials by requesting
    540          them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
    541          header field.
    542       </p>
    543       <div id="rfc.iref.p.2"></div>
    544       <div id="rfc.iref.h.3"></div>
    545       <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="header.proxy-authorization" href="#header.proxy-authorization">Proxy-Authorization</a></h2>
    546       <p id="rfc.section.3.3.p.1">The Proxy-Authorization request-header field allows the client to identify itself (or its user) to a proxy which requires
    547          authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the
    548          user agent for the proxy and/or realm of the resource being requested.
    549       </p>
    550       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span>    Proxy-Authorization     = "Proxy-Authorization" ":" credentials
     548               them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
     549               header field.
     550            </p>
     551         </div>
     552         <div id="header.proxy-authorization">
     553            <div id="rfc.iref.p.2"></div>
     554            <div id="rfc.iref.h.3"></div>
     555            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></h2>
     556            <p id="rfc.section.3.3.p.1">The Proxy-Authorization request-header field allows the client to identify itself (or its user) to a proxy which requires
     557               authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the
     558               user agent for the proxy and/or realm of the resource being requested.
     559            </p>
     560            <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span>    Proxy-Authorization     = "Proxy-Authorization" ":" credentials
    551561</pre><p id="rfc.section.3.3.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.6"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. Unlike Authorization, the Proxy-Authorization header field applies only to the next outbound proxy that demanded authentication
    552          using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
    553          by the first outbound proxy that was expecting to receive credentials. A proxy <em class="bcp14">MAY</em> relay the credentials from the client request to the next proxy if that is the mechanism by which the proxies cooperatively
    554          authenticate a given request.
    555       </p>
    556       <div id="rfc.iref.w.1"></div>
    557       <div id="rfc.iref.h.4"></div>
    558       <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="header.www-authenticate" href="#header.www-authenticate">WWW-Authenticate</a></h2>
    559       <p id="rfc.section.3.4.p.1">The WWW-Authenticate response-header field <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages. The field value consists of at least one challenge that indicates the
    560          authentication scheme(s) and parameters applicable to the Request-URI.
    561       </p>
    562       <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span>    WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
     562               using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
     563               by the first outbound proxy that was expecting to receive credentials. A proxy <em class="bcp14">MAY</em> relay the credentials from the client request to the next proxy if that is the mechanism by which the proxies cooperatively
     564               authenticate a given request.
     565            </p>
     566         </div>
     567         <div id="header.www-authenticate">
     568            <div id="rfc.iref.w.1"></div>
     569            <div id="rfc.iref.h.4"></div>
     570            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></h2>
     571            <p id="rfc.section.3.4.p.1">The WWW-Authenticate response-header field <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages. The field value consists of at least one challenge that indicates the
     572               authentication scheme(s) and parameters applicable to the Request-URI.
     573            </p>
     574            <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span>    WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
    563575</pre><p id="rfc.section.3.4.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.7"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. User agents are advised to take special care in parsing the WWW-Authenticate field value as it might contain more than one
    564          challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
    565          comma-separated list of authentication parameters.
    566       </p>
    567       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    568       <p id="rfc.section.4.p.1">TBD.</p>
    569       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    570       <p id="rfc.section.5.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
    571          as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    572          make some suggestions for reducing security risks.
    573       </p>
    574       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="auth.credentials.and.idle.clients" href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
    575       <p id="rfc.section.5.1.p.1">Existing HTTP clients and user agents typically retain authentication information indefinitely. HTTP/1.1. does not provide
    576          a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
    577          extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
    578          but are not limited to:
    579       </p>
    580       <ul>
    581          <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
    582             the user for credentials.
    583          </li>
    584          <li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which
    585             the server side of the application `knows' that there is no further reason for the client to retain the credentials.
    586          </li>
    587       </ul>
    588       <p id="rfc.section.5.1.p.2">This is currently under separate study. There are a number of work-arounds to parts of this problem, and we encourage the
    589          use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
    590          in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
    591          for discarding cached credentials under user control.
    592       </p>
    593       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    594       <p id="rfc.section.6.p.1">Based on an XML translation of RFC 2616 by Julian Reschke.</p>
     576               challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
     577               comma-separated list of authentication parameters.
     578            </p>
     579         </div>
     580      </div>
     581      <div id="IANA.considerations">
     582         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     583         <p id="rfc.section.4.p.1">TBD.</p>
     584      </div>
     585      <div id="security.considerations">
     586         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     587         <p id="rfc.section.5.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
     588            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
     589            make some suggestions for reducing security risks.
     590         </p>
     591         <div id="auth.credentials.and.idle.clients">
     592            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
     593            <p id="rfc.section.5.1.p.1">Existing HTTP clients and user agents typically retain authentication information indefinitely. HTTP/1.1. does not provide
     594               a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
     595               extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
     596               but are not limited to:
     597            </p>
     598            <ul>
     599               <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
     600                  the user for credentials.
     601               </li>
     602               <li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which
     603                  the server side of the application `knows' that there is no further reason for the client to retain the credentials.
     604               </li>
     605            </ul>
     606            <p id="rfc.section.5.1.p.2">This is currently under separate study. There are a number of work-arounds to parts of this problem, and we encourage the
     607               use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
     608               in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
     609               for discarding cached credentials under user control.
     610            </p>
     611         </div>
     612      </div>
     613      <div id="ack">
     614         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     615         <p id="rfc.section.6.p.1">Based on an XML translation of RFC 2616 by Julian Reschke.</p>
     616      </div>
    595617      <h1 id="rfc.references"><a href="#rfc.section.7" id="rfc.section.7">7.</a> References
    596618      </h1>
    597       <table>     
     619      <table>
    598620         <tr>
    599621            <td class="reference"><b id="Part6">[Part6]</b></td>
    600             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-00">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-00 (work in progress), December&nbsp;2007.
     622            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-00">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-00 (work in progress), December&nbsp;2007.
    601623            </td>
    602624         </tr>
    603625         <tr>
    604626            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    605             <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     627            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    606628            </td>
    607629         </tr>
    608630         <tr>
    609631            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
    610             <td class="top"><a href="mailto:john@math.nwu.edu" title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a href="mailto:pbaker@verisign.com" title="Verisign Inc.">Hallam-Baker, P.</a>, <a href="mailto:jeff@AbiSource.com" title="AbiSource, Inc.">Hostetler, J.</a>, <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">Lawrence, S.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, Luotonen, A., and <a href="mailto:stewart@OpenMarket.com" title="Open Market, Inc.">L. Stewart</a>, “<a href="http://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC&nbsp;2617, June&nbsp;1999.
     632            <td class="top"><a href="mailto:john@math.nwu.edu" title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a href="mailto:pbaker@verisign.com" title="Verisign Inc.">Hallam-Baker, P.</a>, <a href="mailto:jeff@AbiSource.com" title="AbiSource, Inc.">Hostetler, J.</a>, <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">Lawrence, S.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, Luotonen, A., and <a href="mailto:stewart@OpenMarket.com" title="Open Market, Inc.">L. Stewart</a>, “<a href="https://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC&nbsp;2617, June&nbsp;1999.
    611633            </td>
    612634         </tr>
    613635      </table>
    614       <div class="avoidbreak">
    615          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    616          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    617                (editor)
    618                <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
    619          <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:jg@laptop.org"><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
    620          <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:JeffMogul@acm.org"><span class="email">JeffMogul@acm.org</span></a></span></address>
    621          <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:henrikn@microsoft.com"><span class="email">henrikn@microsoft.com</span></a></span></address>
    622          <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems, Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:LMM@acm.org"><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address>
    623          <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a href="mailto:paulle@microsoft.com"><span class="email">paulle@microsoft.com</span></a></span></address>
    624          <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:timbl@w3.org"><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address>
    625       </div>
    626636      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    627637      <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.W">W</a>
     
    630640         <ul class="ind">
    631641            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    632                   <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref."><b>2.1</b></a></li>
    633                   <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.1"><b>2.2</b></a></li>
     642                  <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>2.1</b></a></li>
     643                  <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.2"><b>2.2</b></a></li>
    634644               </ul>
    635645            </li>
     
    689699         </ul>
    690700      </div>
    691       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    692       <p>Copyright © The IETF Trust (2007).</p>
    693       <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    694          authors retain all their rights.
    695       </p>
    696       <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
    697          HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
    698          DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
    699          WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    700       </p>
    701       <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
    702       <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
    703          be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
    704          license under such rights might or might not be available; nor does it represent that it has made any independent effort to
    705          identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
    706          BCP 79.
    707       </p>
    708       <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
    709          of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
    710          of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
    711       </p>
    712       <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
    713          rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
    714          at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
    715       </p>
     701      <div class="avoidbreak">
     702         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     703         <p><b>Roy T. Fielding</b>
     704            (editor)
     705            <br>Day Software<br>23 Corporate Plaza DR, Suite 280<br>Newport Beach, CA&nbsp;92660<br>USA<br>Phone: <a href="tel:+1-949-706-5300">+1-949-706-5300</a><br>Fax: <a href="fax:+1-949-706-5305">+1-949-706-5305</a><br>EMail: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
     706         <p><b>Jim Gettys</b><br>One Laptop per Child<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>EMail: <a href="mailto:jg@laptop.org">jg@laptop.org</a><br>URI: <a href="http://www.laptop.org/">http://www.laptop.org/</a></p>
     707         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>EMail: <a href="mailto:JeffMogul@acm.org">JeffMogul@acm.org</a></p>
     708         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>EMail: <a href="mailto:henrikn@microsoft.com">henrikn@microsoft.com</a></p>
     709         <p><b>Larry Masinter</b><br>Adobe Systems, Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>EMail: <a href="mailto:LMM@acm.org">LMM@acm.org</a><br>URI: <a href="http://larry.masinter.net/">http://larry.masinter.net/</a></p>
     710         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>EMail: <a href="mailto:paulle@microsoft.com">paulle@microsoft.com</a></p>
     711         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>EMail: <a href="mailto:timbl@w3.org">timbl@w3.org</a><br>URI: <a href="http://www.w3.org/People/Berners-Lee/">http://www.w3.org/People/Berners-Lee/</a></p>
     712      </div>
     713      <div id="rfc.copyright">
     714         <h1><a href="#rfc.copyright">Full Copyright Statement</a></h1>
     715         <p>Copyright © The IETF Trust (2007).</p>
     716         <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
     717            authors retain all their rights.
     718         </p>
     719         <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
     720            HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
     721            DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
     722            WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
     723         </p>
     724      </div>
     725      <div id="rfc.ipr">
     726         <h1><a href="#rfc.ipr">Intellectual Property</a></h1>
     727         <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
     728            be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
     729            license under such rights might or might not be available; nor does it represent that it has made any independent effort to
     730            identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
     731            BCP 79.
     732         </p>
     733         <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
     734            of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
     735            of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
     736         </p>
     737         <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
     738            rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
     739            at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
     740         </p>
     741      </div>
    716742   </body>
    717743</html>
Note: See TracChangeset for help on using the changeset viewer.