Return error code: 401 unauthorized, 401 unauthorized

Return error code: 401 unauthorized, 401 unauthorized
ZookeeperReturn error code: 401 unauthorized indicates that the http return code is unauthorized, And the account and password are not entered. Therefore, the solution is to directly carry the password in the HTTP package. Use shell to generate base64 encoding for user and password

Encode the account admin and password admin information with base64 as YWRtaW46YWRtaW4 =.

$ echo -n admin：admin | base64YWRtaW46YWRtaW4=

You can also use the results to verify whether the account is admin and the password is admin.

$ echo -n YWRtaW46YWRtaW4= | base64 -d

admin：admin 

After obtaining the base64 encoded result, add the following in the HTTP format of the get request:

Authorization: Basic YWRtaW46YWRtaW4=

The 401 error code problem can be solved.

Attach the HTTP Error code table:

All HTTP status codes and definitions. The Code indicates that 2xx is successful and 200 is normal. The request has been completed. 201 normal; followed by the POST command. 202 normal; accepted for processing, but not completed. 203 normal; partial information-only part of the returned information. 204 normal; no response-received request, but no information to send back. 3xx redirection 301 moved-the requested data has a new location and the change is permanent. 302 found-the requested data temporarily has different Uris. 303 refer to others-you can find the response to the request under another URI and use the GET method to retrieve the response. 304 not modified-the document was not modified as expected. 305 use proxy-the requested resource must be accessed through the proxy provided in the location field. 306 not used-no longer used; keep this code for future use. 4xx client error 400 Error request-the request has a syntax problem or cannot meet the request. 401 unauthorized-unauthorized client access to data. 402 payment required-the billing system is in effect. 403 forbidden-access is not required even if authorized. 404 Not found-the server cannot find the specified resource; the document does not exist. 407 proxy authentication request-the client must first use proxy authentication itself. 415 the media type is not supported-the server rejects service requests because the Request Entity format is not supported. 5xx Server Error 500 internal error-the server cannot complete the request due to exceptions. 501 not executed-the server does not support the requested tool. 502 error gateway-the server receives an invalid response from the upstream server. 503 unable to obtain services-the server cannot process requests due to temporary overload or maintenance.

Zookeeper
HTTP: 4013-Unauthorized

Go to the site folder J: \ WebSite \ AnGe. Click index.htm to view the attributes. Add the inter Guest user in the Security Section, that is, the user starting with IUSR _. the IUSR _ permission for a single folder is insufficient. The htm file must also have the IUSR _ permission.

Failed due to HTTP status 401: Unauthorized reason?

HTTP 400-invalid request
HTTP 401.1-unauthorized: Logon Failed
HTTP 401.2-unauthorized: logon fails due to server configuration problems
HTTP 401.3-ACL prohibit Resource Access
HTTP 401.4-unauthorized: Authorization denied by filter
HTTP 401.5-unauthorized: ISAPI or CGI authorization failed
401-Access denied. IIS defines many different 401 errors, which indicate more specific error causes. These specific error codes are displayed in the browser, but not in the IIS log :?? 401.1-Logon Failed.
?? 401.2-login failed due to server configuration.
?? 401.3-the ACL is not authorized due to resource restrictions.
?? 401.4-filter authorization failed.
?? 401.5-An error occurred while authorizing the ISAPI/CGI application.
?? 401.7-the access is rejected by the URL Authorization Policy on the Web server. This error code is dedicated to IIS 6.0.