I am grateful to Joyce for my guidance in the front-end, under the guidance of the Great God, I found that the more I understand the front end like it, the front-end learning to the back like an art, full of fun.
Recently made a short-term study plan, found that for me super useful, well-organized, can take a lot less detours, straight to the subject AH
HTTP 状态消息
First I will look at each status code and the corresponding word (eg:200 OK, 304 No Modified, 404 Not Found), and then understand the word behind the large paragraph of the text description, according to their own understanding summed up a short paragraph, and finally all connected together memory. "Take a moment to look and you will find not much!" "When a browser reports a status code, it usually follows the status code with the corresponding word." "The blue of its bid means what I see."
1** (Information Class): Indicates receipt of the request and continues processing
continue--customer must continue to make a request
101 Switch protocols--client requests that the server convert the HTTP protocol version on request
102 processing--representative processing will continue to execute
103 checkpoint--recommended for recovery requests when a put or POST request recovery fails
2** (Successful response): Indicates that the action was successfully received, understood, and accepted
200 ok--indicates that the request was successfully completed and the requested resource was sent back to the client
20 1 The created--request is created and the new resource is created
202 accept--for processing the request has been accepted, but processing is not completed
203 non-authoritative information--return information is not OK or incomplete
204 no content--request received, but return information is empty
205 Reset content--Server completed the request with The user agent must reset the file that is currently browsed
206 partial content--server has completed the GET request for some users
3** (redirect Class): To complete a specified action, you must accept further processing
Multiple choices--requested resources can be obtained in multiple places
301 Move permanently--This page is permanently transferred to another URL
302 found--The requested page has been temporarily transferred to the new URL
303 See other--advising customers to access other URLs or access methods
304 No modified--did not modify the document as expected, the server tells the customer that the original buffered document can continue to use
305 use proxy--The requested resource must be obtained from the address specified by the server
306 Switch proxy--The code used in the previous version of HTTP, which is no longer used in the current version
307 temporary redirect--The requested resource is now temporarily responding to requests from different URIs
308 Resume incomplete--is recommended for recovery requests when a put or POST request recovery fails.
4** (Client Error Class): Request contains error syntax or does not execute correctly
The bad request--client request has a syntax error and cannot be understood by the server
401 unauthorized--A legitimate request, but access to the requested page is prohibited.
HTTP 401.1-Unauthorized: Logon failed
HTTP 401.2-Unauthorized: Server configuration issues cause logon failure
HTTP 401.3-acl prohibit access to resources
HTTP 401.4-Unauthorized: Authorization denied by filter
HTTP 401.5-Unauthorized: ISAPI or CGI authorization failed
402 Payment required--reserved effective Chargeto head response
403 forbidden--Forbidden, the server receives the request but refuses to provide service
HTTP 403.1-Forbidden: Disable executable access
HTTP 403.2-Forbidden: Disable Read access
HTTP 403.3-Forbidden: write-Access Forbidden
HTTP 403.4-No access: SSL required
HTTP 403.5-No access: SSL 128 required
HTTP 403.6-Forbidden: IP address denied
HTTP 403.7-Forbidden: Require client certificate
HTTP 403.8-Forbidden: Prohibit site access
HTTP 403.9-No access: too many users connected
HTTP 403.10-No access: Invalid configuration
HTTP 403.11-No access: Password change
HTTP 403.12-No access: Mapper denied access
HTTP 403.13-No access: Client certificate has been revoked
HTTP 403.15-No access: Too many Client access licenses
HTTP 403.16-Forbidden: Client certificate is untrusted or invalid
HTTP 403.17-Forbidden: Client certificate has expired or is not yet valid
404 Not found--Server could not find the requested page
405 Method not allowed--user defined in the Request-line field does not allow
The content attribute of the resource requested by 406 not acceptable--cannot satisfy the condition in the request header, so the response entity cannot be generated.
407 Proxy authentication require--similar to 401, the user must first be authorized on the proxy server
408 Request timeout--Client does not complete requests within a user-specified time
409 conflict--The request cannot be completed due to a conflict
410 gone--The requested page is not available
411 Length repuire--Server rejects user-defined Content-length property requests
412 Precondition failed--request is evaluated by the server as failed
413 Request Entity Too large--The requested resource is greater than the size allowed by the server
414 Request-uri Too long--The requested resource URL is longer than the length allowed by the server
415 Unsupported Media type--requesting a resource does not support requesting an item format
416 Request Range not satisfiable--client requests part of the document, but the server cannot provide the requested part
417 Expectation failed--Server does not meet the request header specified by the customer in the request
5** (Service-side error Class): The server does not correctly execute a correct request
Internal Server Error-the server encountered an error and could not complete the request
HTTP 500.100-Internal server error
HTTP 500-11 Server shutdown
HTTP 500-12 Application Restart
HTTP 500-13-Server Too busy
HTTP 500-14-Application not valid
HTTP 500-15-Request not allowed
501 not implement--request not completed
502 Bad gateway--Gateway error
503 Service unavailable--Server is currently unavailable
504 Gateway timeout--Gateways Timeout
505 HTTP Version Not supported--server does not support the HTTP protocol version indicated in the request
511 Network authentication required--users need to provide authentication to get access to the Web
HTTP Status Messages