![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 2120 for draft-ietf-httpbis/latest
- Timestamp:
- 13/01/13 11:34:03 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
-
p2-semantics.html (modified) (10 diffs)
-
p2-semantics.xml (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2119 r2120 2020 2020 </div> 2021 2021 <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a> <a id="request.auth" href="#request.auth">Authentication Credentials</a></h2> 2022 <p id="rfc.section.5.4.p.1">Two header fields are used for carrying authentication credentials, as defined in <a href="#Part7" id="rfc.xref.Part7.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>. Note that various custom mechanisms for user authentication use the Cookie header field for this purpose, as defined in <a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>. 2023 </p> 2022 2024 <div id="rfc.table.u.7"> 2023 2025 <table class="tt full left" cellpadding="3" cellspacing="0"> … … 2031 2033 <tr> 2032 2034 <td class="left">Authorization</td> 2033 <td class="left"><a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7. 2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>2035 <td class="left"><a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td> 2034 2036 </tr> 2035 2037 <tr> 2036 2038 <td class="left">Proxy-Authorization</td> 2037 <td class="left"><a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a> of <a href="#Part7" id="rfc.xref.Part7. 3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>2039 <td class="left"><a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a> of <a href="#Part7" id="rfc.xref.Part7.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td> 2038 2040 </tr> 2039 2041 </tbody> … … 2041 2043 </div> 2042 2044 <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a> <a id="request.context" href="#request.context">Request Context</a></h2> 2045 <p id="rfc.section.5.5.p.1">The following request header fields provide additional information about the request context, including information about 2046 the user, user agent, and resource behind the request. 2047 </p> 2043 2048 <div id="rfc.table.u.8"> 2044 2049 <table class="tt full left" cellpadding="3" cellspacing="0"> … … 2162 2167 </ul> 2163 2168 <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="overview.of.status.codes" href="#overview.of.status.codes">Overview of Status Codes</a></h2> 2164 <p id="rfc.section.6.1.p.1">The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7. 4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the2169 <p id="rfc.section.6.1.p.1">The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by local equivalents without affecting the 2165 2170 protocol. 2166 2171 </p> … … 2263 2268 <td class="left">401</td> 2264 2269 <td class="left">Unauthorized</td> 2265 <td id="status.401" class="left"><a href="p7-auth.html#status.401" title="401 Unauthorized">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7. 5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>2270 <td id="status.401" class="left"><a href="p7-auth.html#status.401" title="401 Unauthorized">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td> 2266 2271 </tr> 2267 2272 <tr> … … 2293 2298 <td class="left">407</td> 2294 2299 <td class="left">Proxy Authentication Required</td> 2295 <td id="status.407" class="left"><a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 3.2</a> of <a href="#Part7" id="rfc.xref.Part7. 6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>2300 <td id="status.407" class="left"><a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 3.2</a> of <a href="#Part7" id="rfc.xref.Part7.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td> 2296 2301 </tr> 2297 2302 <tr> … … 3041 3046 other than the method and request target, unless the variance cannot be crossed or the origin server has been deliberately 3042 3047 configured to prevent cache transparency. For example, there is no need to send the Authorization field name in Vary because 3043 reuse across users is constrained by the field definition (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7. 7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>). Likewise, an origin server might use Cache-Control directives (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to supplant Vary if it considers the variance less significant than the performance cost of Vary's impact on caching.3048 reuse across users is constrained by the field definition (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>). Likewise, an origin server might use Cache-Control directives (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to supplant Vary if it considers the variance less significant than the performance cost of Vary's impact on caching. 3044 3049 </p> 3045 3050 <div id="rfc.iref.s.8"></div> … … 3089 3094 <tr> 3090 3095 <td class="left">WWW-Authenticate</td> 3091 <td class="left"><a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a> of <a href="#Part7" id="rfc.xref.Part7. 8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>3096 <td class="left"><a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a> of <a href="#Part7" id="rfc.xref.Part7.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td> 3092 3097 </tr> 3093 3098 <tr> 3094 3099 <td class="left">Proxy-Authenticate</td> 3095 <td class="left"><a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7. 9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>3100 <td class="left"><a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td> 3096 3101 </tr> 3097 3102 </tbody> … … 4661 4666 </ul> 4662 4667 </li> 4663 <li><em>Part7</em> <a href="#rfc.xref.Part7.1">4.3.8</a>, <a href="#rfc.xref.Part7.2">5.4</a>, <a href="#rfc.xref.Part7.3">5.4</a>, <a href="#rfc.xref.Part7.4"> 6.1</a>, <a href="#rfc.xref.Part7.5">6.1</a>, <a href="#rfc.xref.Part7.6">6.1</a>, <a href="#rfc.xref.Part7.7">7.1.4</a>, <a href="#rfc.xref.Part7.8">7.3</a>, <a href="#rfc.xref.Part7.9">7.3</a>, <a href="#Part7"><b>11.1</b></a><ul>4664 <li><em>Section 3</em> <a href="#rfc.xref.Part7. 4">6.1</a></li>4665 <li><em>Section 3.1</em> <a href="#rfc.xref.Part7. 5">6.1</a></li>4666 <li><em>Section 3.2</em> <a href="#rfc.xref.Part7. 6">6.1</a></li>4667 <li><em>Section 4.1</em> <a href="#rfc.xref.Part7. 2">5.4</a>, <a href="#rfc.xref.Part7.7">7.1.4</a></li>4668 <li><em>Section 4.2</em> <a href="#rfc.xref.Part7. 9">7.3</a></li>4669 <li><em>Section 4.3</em> <a href="#rfc.xref.Part7. 3">5.4</a></li>4670 <li><em>Section 4.4</em> <a href="#rfc.xref.Part7. 8">7.3</a></li>4668 <li><em>Part7</em> <a href="#rfc.xref.Part7.1">4.3.8</a>, <a href="#rfc.xref.Part7.2">5.4</a>, <a href="#rfc.xref.Part7.3">5.4</a>, <a href="#rfc.xref.Part7.4">5.4</a>, <a href="#rfc.xref.Part7.5">6.1</a>, <a href="#rfc.xref.Part7.6">6.1</a>, <a href="#rfc.xref.Part7.7">6.1</a>, <a href="#rfc.xref.Part7.8">7.1.4</a>, <a href="#rfc.xref.Part7.9">7.3</a>, <a href="#rfc.xref.Part7.10">7.3</a>, <a href="#Part7"><b>11.1</b></a><ul> 4669 <li><em>Section 3</em> <a href="#rfc.xref.Part7.5">6.1</a></li> 4670 <li><em>Section 3.1</em> <a href="#rfc.xref.Part7.6">6.1</a></li> 4671 <li><em>Section 3.2</em> <a href="#rfc.xref.Part7.7">6.1</a></li> 4672 <li><em>Section 4.1</em> <a href="#rfc.xref.Part7.3">5.4</a>, <a href="#rfc.xref.Part7.8">7.1.4</a></li> 4673 <li><em>Section 4.2</em> <a href="#rfc.xref.Part7.10">7.3</a></li> 4674 <li><em>Section 4.3</em> <a href="#rfc.xref.Part7.4">5.4</a></li> 4675 <li><em>Section 4.4</em> <a href="#rfc.xref.Part7.9">7.3</a></li> 4671 4676 </ul> 4672 4677 </li> … … 4752 4757 <li><em>RFC5987</em> <a href="#rfc.xref.RFC5987.1">8.3.1</a>, <a href="#RFC5987"><b>11.2</b></a></li> 4753 4758 <li><em>RFC5988</em> <a href="#rfc.xref.RFC5988.1">6.4.1</a>, <a href="#RFC5988"><b>11.2</b></a></li> 4754 <li><em>RFC6265</em> <a href="#rfc.xref.RFC6265.1">4.3.8</a>, <a href="# RFC6265"><b>11.2</b></a></li>4759 <li><em>RFC6265</em> <a href="#rfc.xref.RFC6265.1">4.3.8</a>, <a href="#rfc.xref.RFC6265.2">5.4</a>, <a href="#RFC6265"><b>11.2</b></a></li> 4755 4760 <li><em>RFC6266</em> <a href="#RFC6266"><b>11.2</b></a>, <a href="#rfc.xref.RFC6266.1">B</a></li> 4756 4761 <li><em>RFC6365</em> <a href="#rfc.xref.RFC6365.1">1.2</a>, <a href="#rfc.xref.RFC6365.2">3.1.1.2</a>, <a href="#RFC6365"><b>11.1</b></a></li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2119 r2120 2359 2359 2360 2360 <section title="Authentication Credentials" anchor="request.auth"> 2361 <t> 2362 Two header fields are used for carrying authentication credentials, as 2363 defined in <xref target="Part7"/>. Note that various custom mechanisms for 2364 user authentication use the Cookie header field for this purpose, as 2365 defined in <xref target="RFC6265"/>. 2366 </t> 2361 2367 <texttable align="left"> 2362 2368 <ttcol>Header Field Name</ttcol> … … 2369 2375 2370 2376 <section title="Request Context" anchor="request.context"> 2377 <t> 2378 The following request header fields provide additional information about the 2379 request context, including information about the user, user agent, and 2380 resource behind the request. 2381 </t> 2371 2382 <texttable align="left"> 2372 2383 <ttcol>Header Field Name</ttcol>
Note: See TracChangeset
for help on using the changeset viewer.
