Http StatuCode description and httpstatucode description

Http StatuCode description and httpstatucode description

Http description:

Http 200:-The file is normally accessed.

Http 302: Temporary redirection

HTTP Error List

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

HTTP 403-Access prohibited

HTTP 403-access to Internet Service Manager (HTML) is limited to Localhost

HTTP 403.1 Prohibit Access: Prohibit executable access

HTTP 403.2-Access prohibited: Read prohibited

HTTP 403.3-Access prohibited: Write Access prohibited

HTTP 403.4-Access prohibited: requires SSL

HTTP 403.5-Access prohibited: requires SSL 128

HTTP 403.6-Access prohibited: the IP address is denied

HTTP 403.7-Access prohibited: client certificate required

HTTP 403.8-Access prohibited: site access prohibited

HTTP 403.9-Access prohibited: too many connected users

HTTP 403.10-Access prohibited: Invalid Configuration

HTTP 403.11-Access prohibited: Password Change

HTTP 403.12-Access prohibited: mappers reject access

HTTP 403.13-Access prohibited: the client certificate has been revoked

HTTP 403.15-Access prohibited: too many access permits from customers

HTTP 403.16-Access prohibited: the client certificate is untrusted or invalid

HTTP 403.17-Access prohibited: the client certificate has expired or has not yet taken effect

HTTP 404.1-not foundWebSite

HTTP 404-file not found

HTTP 405-the resource is forbidden

HTTP 406-unacceptable

HTTP 407-proxy authentication required

HTTP 410-never available

HTTP 412-precondition failed

HTTP 414-request-URI is too long

HTTP 500-Internal Server Error

HTTP 500.100-Internal Server Error-ASP Error

HTTP 500-11 Server Disabled

HTTP 500-12 Application restart

HTTP 500-13-the server is too busy

HTTP 500-14-invalid Application

HTTP 500-15-requests to global. asa are not allowed

Error 501-not implemented

HTTP 502-Gateway error

 

Error Codes and Status Codes

Recently, some friends have asked cPanel about the meaning of "HTTP Error Code (HTTP Error codes)" in Awstats, and whether to pay attention to and handle it.

For more information about Awstats, see CP How-To: How To Use cPanel To view site statistics (awstats)

Article address:

Http://bbs.netpu.net/viewthread.php? Tid = 694

In fact, this is a misunderstanding. Here it should be "HTTP Status code (HTTP Status codes )".

OK. Since it is a status code, there may be two States: Correct and wrong (at least not all of them are wrong. Let's take a sigh of relief ). What do these codes mean? What are the error states and the correct ones? Don't worry. Let's give a brief introduction to the impersonating internal behavior below.

HTTP and Status codes

HTTP is a hypertext transfer protocol. The browser communicates with the WEB Server over HTTP (some other software, such as IM, uses the HTTP protocol to transmit data), transmits our Request (HTTP Request) to the Server, and the Server responds to this Request, return the HTTP Response and the data we need. This is basically what it looks like.

If we request something, the server will return something, so HTTP Status codes is not needed. But things are often not that simple. For example, if we request a webpage, but the server does not, or the webpage is transferred to another place, or the server disallows us to view the webpage, therefore, in order to facilitate the browser to handle these correct and incorrect situations, HTTP uses Status codes to indicate that the Request (HTTP Request) is processed on the server. Status codes returns the Response to the browser through HTTP Response. The browser will handle the Response accordingly.

HTTP Status codes Classification

Since there are both correct and wrong statuses, does HTTP define two types of status codes? People develop agreements, but experts (unlike me) think more carefully than we do. Five major types of Status codes are defined in HTTP 1.1:

Informational

Meaning: Information

Range: 1XX

Successful

Meaning: Successful

Range: 2XX

Redirection

Meaning: Redirection

Value Range: 3XX

Client Error

Meaning: client errors

Range: 4XX

Server Error

Meaning: Server Error

Range: 5XX

Look at how thoughtful people think. Real experts are real experts.

Introduction to common HTTP Status codes

Next we will briefly introduce the HTTP Status codes that we often encounter.

It may be that I am ignorant. I often encounter a few HTTP Status codes.

Successful

200-OK: OK

This is the most common one (we may not see it directly, but if you use some packet capture tools, most http responses have this ). The meaning is very simple, that is, the server receives and understands the client requests and processes them normally.

206-Partial Content: Partial Content.

This also happens frequently. It is easy for everyone to publish messages.

In layman's terms, if the client requests a part of the content of the document (image, text, sound, etc.) and the server processes the content normally, 206 is returned. In general, in addition to specifying the request content, it also specifies the offset and length.

Some content, right? This is why many browsers and software support resumable data transfer. Haha, don't be afraid to see 206 in the future.

Redirection

301-Moved Permanently: Permanently Moved.

This status code indicates that the resources requested by the client have been permanently transferred to a new place. This Response (HTTP Response) also contains the new address of the resource. It tells the client that if you want this resource again next time, you can use the new address to retrieve it.

302 Found: Temporary redirection.

This status code indicates that the resources requested by the client are temporarily put in a new place. The response also contains the new address of the resource.

307-Temporary Redirect: Temporary redirection. (If we don't implement the Protocol or perform related development, we can roughly understand it as much as 302)

Client Error

400-Bad Request: Incorrect Request

The request syntax is incorrect and cannot be understood by the server.

401-Unauthorized: Unauthorized

When the server returns 401 Code, it indicates that the client must be authorized by the server before accessing the specified resource.

403-Forbidden: Access prohibited

That is, access to some resources is not allowed.

404-Not Found: Not Found

Client request content not found

Server Error

500-Internal Server Error

Internal Server error.

Conclusion

The more you write, the more lazy it is. It is useless. It would be nice for me to eliminate one or two questions about this. Since we have already said that we are impersonating experts, it is inevitable that there are mistakes and mistakes.

Do not read this article to avoid being misled by this article. PleaseLearningOfficial agreement content.

Official materials:

 

Source File http://www.51testing.com /? 134114/action_viewspace_itemid_99305.html

 

 

Http error codes

 

400 invalid syntax. syntax problems

401 access denied. access denied

402 payment required. Must be complete

403 request forbidden. The request is forbidden.

404 object not found. The object is not found.

405 method is not allowed. The method is not allowed

406 no resp acceptable to client found. The client has no response

407 proxy authentication required. The proxy needs to be verified

408 server timed out waiting for request. The server is disconnected when a request is made.

409 user shocould resubmit with more info. Check for conflicting users

410 resource is no l available. The resource is unavailable

411 server refused to accept request without a length. The server rejects requests with no length.

412 prec given in request failed. Discard the request failure condition

413 request entity was too large. The request is too large

414 request uniform resource identifier (uri) too long. The request uri is too long

415 unsupported media type. media type is not supported

449 retry after doing the appropriate action. retry after performing the appropriate action

500 internal server error. An internal server error occurs.

501 server does not support the functi required to fulfill the request. the server does not support the request Function

502 error resp received ed from gateway. Receive error response from gateway

503 temporarily overloaded. Overload

504 timed out waiting for gateway. Request to be disconnected while waiting for gateway

505 http version not supported. http version not supported

 

 

Http status codes returned by servers on the internet.

Http status code returned from the internet (http status word)

Http_status_continue (100)

The request can be continued.

The request cannot be continued.

Http_status_switch_protocols (101)

The server has switched protocols in an upgrade header.

The new header server protocol is converted.

Http_status_okay (200)

The request completed successfully.

Successful request Completion

Http_status_created (201)

The request has been fulfilled and resulted in the creation of a new resource.

The new resource request has been completed.

Http_status_accepted( 202)

The request has been accepted for processing, but the processing has not been completed.

The request has been processed, but the process has not been completed.

Http_status_partial (203)

The returned meta information in the entity-header is not the definitive set available from the origin server.

The meta information returned by the slave server in the entity-header is invalid.

Http_status_no_content (204)

The server has fulfilled the request, but there is no new information to send back.

The server implements the request but does not return information

Http_status_reset_content (205)

The request has been completed, and the client program shocould reset the document view that caused the request to be sent to allow the user to easily initiate another input action.

The request has been completed, and the web program (client program browser program) has reset the document view directory (c

Http_status_partial_content (206)

The server has fulfilled the partial get request for the resource.

The server has completed some get requests for the resource.

Http_status_ambiguous (300)

The server couldn't decide what to return.

The server cannot determine what is returned

Http_status_moved (301)

The requested resource has been assigned to a new permanent uri (uniform resource identifier), and any future references to this resource shocould be d using of the returned uris.

The requested resource has been allocated to a new uri and will be used for future reference.

Http_status_redirect (302)

The requested resource resides temporarily under a different uri (uniform resource identifier ).

The requested resource is temporarily under different Uris

Http_status_redirect_method (303)

The resp to the request can be found under a different uri (uniform resource identifier) and shocould be retrieved using a get http verb on that resource.

Requested resources cannot be found under different Uris, AND get http is used to retrieve resources from the server.

Http_status_not_modified (304)

The requested resource has not been modified.

Requested resource not changed

Http_status_use_proxy (305)

The requested resource must be accessed through the proxy given by the location field.

The requested resource must be obtained through a specific proxy.

Http_status_redirect_keep_verb (307)

The redirected request keeps the same http verb. http/1.1 behav failed or.

From locating requests,

Http_status_bad_request (1, 400)

The request cocould not be processed by the server due to invalid syntax.

Because the syntax cannot be processed by the server

Http_status_denied (401)

The requested resource requires user authentication.

The request resource command must be verified (Access denied)

Http_status_payment_req (402)

Not currently implemented in the http protocol.

Http protocol not fully implemented

Http_status_forbidden (403)

The server understood the request, but is refusing to fulfill it.

The server understands the request but rejects the request.

Http_status_not_found (404)

The server has not found anything matching the requested uri (uniform resource identifier ).

No specified uri found

 

Http_status_bad_method (405)

The http verb used is not allowed.

Http action not allowed

Http_status_none_acceptable (406)

No resp acceptable to the client were found.

The response is not accepted by the customer.

Http_status_proxy_auth_req (407)

Proxy authentication required.

The proxy must be verified.

Http_status_request_timeout (408)

The server timed out waiting for the request.

The server is suspended while waiting for the request.

Http_status_conflict (409)

The request cocould not be completed due to a c with the current state of the resource. the user shocould resubmit with more information.

The request cannot be completed. The problem is resource conflict. Users should make adjustments

Http_status_gone (410)

The requested resource is no l available at the server, and no forwarding address is known.

The requested resource is no longer available on the server and there is no forwarding address

Http_status_length_required( 411)

The server refuses to accept the request without a defined c length.

The server rejects requests that do not define the directory size.

Http_status_precond_failed (412)

The prec given in or more of the request header fields evaluated to false when it was tested on the server.

When on the serverTestThe request header file waives one or more request conditions.

Http_status_request_too_large (413)

The server is refusing to process a request because the request entity is larger than the server is willing or able to process.

The server rejects the request because the request size exceeds the size that the server can process.

Http_status_uri_too_long (414)

The server is refusing to service the request because the request uri (uniform resource identifier) is l than the server is willing to interpret.

The server rejects the service because the requested uri exceeds the length that the server can reveal.

Http_status_unsupportorted_media (415)

The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.

The server rejects the service because the request format is not supported.

Http_status_retry_with (449)

The request shoshould be retried after doing the appropriate action.

The request is retried after an appropriate action is taken

Http_status_server_error (500)

The server encountered an unexpected c that prevented it from fulfilling the request.

Server Request failure

Http_status_not_supported (501)

The server does not support the functi required to fulfill the request.

The server does not support the function that must complete the request.

Http_status_bad_gateway (502)

The server, while acting as a gateway or proxy, received an invalid resp from the upstream server it accessed in attempting to fulfill the request.

When the server acts as a gateway or proxy, the response request received from the upstream server fails.

Http_status_service_unavail (503)

The service is temporarily overloaded.

Server Load

Http_status_gateway_timeout (504)

The request was timed out waiting for a gateway.

Request disconnected while waiting for gateway, no response

Http_status_version_not_sup (505)

The server does not support, or refuses to support, the http protocol version that was used in the request message.

The server does not support or rejects the version of the http protocol in use.

 

Source File http://www.51testing.com /? 26285/action_viewspace_itemid_18747.html