401 Parse Error

HTTP 401 Error-Not authorized: (Unauthorized)

introduce

Your Web server believes that the client (such as your browser or our Checkupdown robot) sends the HTTP data stream is correct, but enters the URL (URL) resource, requires user authentication, and the relevant information 1 has not yet been provided, or 2 has not passed the authorization test. This is what is commonly known as "HTTP Basic authentication." The authentication request provided by the client is defined in the HTTP protocol as the www– Validation header field (www-authenticate header fields).

In general, the error message indicates that you first need to log on (enter a valid username and password). If you just enter this information, you see a 401 error immediately, which means that for whatever reason your username and password are not valid (input is incorrect, user name is temporarily deactivated, etc.).

401 errors in the HTTP loop

Any client (such as your browser or our Checkupdown robot) needs to get an IP address from the IP name of your site (that is, the URL of your site-url, without the start of ' http://'). This correspondence (that is, the correspondence between IP names and IP address conversions) is provided by the Domain name server (DNSS). Open an IP socket (socket) to connect to the IP address. Writes an HTTP data stream through this socket. The HTTP data stream that receives the response from your Web server. The data flow includes a state encoding whose value depends on the HTTP protocol. Resolves the data stream to obtain status codes and other useful information.

This error is generated in the last step described above, that is, when the client receives an HTTP status code and recognizes it as ' 401 '

Resolve 401 Errors-General method

Each Web server has its own way of managing user authentication. Typically, a network security member of the Web site (for example, a system administrator) determines which users are allowed access to the Web site. The person uses WEB Server software to establish the user name and password for these users. Therefore, if you need to access a URL (or you forget your username and password), only the network security officer of that site can help you. Any security issues need to be submitted directly to them.

If you think the page on the site * should * be open to any Internet user, then 401 of the information indicates a deeper problem. First, you can check your URL through a browser. The browser should run on a computer that you have never used before, and that does not contain any information about you, and you should also avoid using the authentication (password, etc.) you have used before. Ideally, this should be done through a completely different internet connection than any one you've ever used (for example, a dial-up connection provided by a different Internet service provider-ISP). In short, you want to simulate the situation where a complete stranger accesses your Web page by surfing the web.

If this browser-checking indicates that there is no licensing issue, your WEB server (or perimeter system) may be set to disallow some kind of HTTP transfer mode. In other words, HTTP traffic from a well-known browser is allowed, but automatic communication from other systems is rejected and generates 401 error codes. This is an exception, but it may indicate a very defensive security policy around your WEB server.

Resolve 401 Error –checkupdown

When you set up your Checkupdown account, you can selectively provide two items of information 2. Website username , and 3. Website Password . You should provide this information only if your site uses HTTP Basic authentication. If you provide this information, checkupdown robots will always use them. If your site does not actually use Basic authentication, it can cause a 401 error. Conversely, if you do not provide this information, and your site uses this authentication, you will also get a 401 error.

However, if your Web site is open to all visitors, 401 of the information should not be present. Because it indicates a basic licensing issue, we can only solve the problem by consulting with the people responsible for your website and the security of the perimeter system. Unfortunately, these discussions may take some time, but tend to be amicably resolved. You can help solve the problem by recommending our services to your system security personnel. If you continue to find 401 errors, please contact us (preferably via email) so that we can agree on the best way to solve these problems.

From: http://blog.csdn.net/patronsaint/article/details/5639962