Changeset 39 for draft-ietf-httpbis/latest/p7-auth.xml
- Timestamp:
- 18/12/07 00:22:08 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p7-auth.xml
r36 r39 192 192 </t> 193 193 </section> 194 195 <section title="Status Code Definitions"> 196 <section title="401 Unauthorized" anchor="status.401"> 197 <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/> 198 <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/> 199 <t> 200 The request requires user authentication. The response &MUST; include a 201 WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge 202 applicable to the requested resource. The client &MAY; repeat the 203 request with a suitable Authorization header field (<xref target="header.authorization"/>). If 204 the request already included Authorization credentials, then the 401 205 response indicates that authorization has been refused for those 206 credentials. If the 401 response contains the same challenge as the 207 prior response, and the user agent has already attempted 208 authentication at least once, then the user &SHOULD; be presented the 209 entity that was given in the response, since that entity might 210 include relevant diagnostic information. HTTP access authentication 211 is explained in "HTTP Authentication: Basic and Digest Access 212 Authentication" <xref target="RFC2617"/>. 213 </t> 214 </section> 215 <section title="407 Proxy Authentication Required" anchor="status.407"> 216 <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/> 217 <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/> 218 <t> 219 This code is similar to 401 (Unauthorized), but indicates that the 220 client must first authenticate itself with the proxy. The proxy &MUST; 221 return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a 222 challenge applicable to the proxy for the requested resource. The 223 client &MAY; repeat the request with a suitable Proxy-Authorization 224 header field (<xref target="header.proxy-authorization"/>). HTTP access authentication is explained 225 in "HTTP Authentication: Basic and Digest Access Authentication" 226 <xref target="RFC2617"/>. 227 </t> 228 </section> 229 </section> 230 194 231 <section title="Header Field Definitions" anchor="header.fields"> 195 232 <t>
Note: See TracChangeset
for help on using the changeset viewer.