b6489e3c-7a1a-4384-8144-db22037f64ad_result.xml
| 1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
|
|---|---|
| 2 |
<HTML>
|
| 3 |
<HEAD>
|
| 4 |
<TITLE>Error 401--Unauthorized</TITLE> |
| 5 |
</HEAD>
|
| 6 |
<BODY bgcolor="white"> |
| 7 |
<FONT FACE=Helvetica><BR CLEAR=all> |
| 8 |
<TABLE border=0 cellspacing=5><TR><TD><BR CLEAR=all> |
| 9 |
<FONT FACE="Helvetica" COLOR="black" SIZE="3"><H2>Error 401--Unauthorized</H2> |
| 10 |
</FONT></TD></TR>
|
| 11 |
</TABLE>
|
| 12 |
<TABLE border=0 width=100% cellpadding=10><TR><TD VALIGN=top WIDTH=100% BGCOLOR=white><FONT FACE="Courier New"><FONT FACE="Helvetica" SIZE="3"><H3>From RFC 2068 <i>Hypertext Transfer Protocol -- HTTP/1.1</i>:</H3> |
| 13 |
</FONT><FONT FACE="Helvetica" SIZE="3"><H4>10.4.2 401 Unauthorized</H4> |
| 14 |
</FONT><P><FONT FACE="Courier New">The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.46) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity MAY include relevant diagnostic information. HTTP access authentication is explained in section 11.</FONT></P> |
| 15 |
</FONT></TD></TR>
|
| 16 |
</TABLE>
|
| 17 |
|
| 18 |
</BODY>
|
| 19 |
</HTML>
|