We in the code on-line, or Web server anomalies, we can provide feedback to our status code, go about locating the fault point, and then through the log to detailed analysis, so the status code is still very important, but in the online rough search, dense a lot of, or their own summary, usually the most commonly used several, Hope to be helpful to everyone;
Web page status code, detailed description:
Status code
|
Status description
|
200
|
OK to successfully return the Web page on behalf of the server
|
301
|
Permanent jump, permanent jump through the old URL to the new URL, ( I have a new name, you find it to go )
|
60W
|
Temporary jump, a period of time to jump to the new URL address access
|
403
|
Forbidden access, server denied access ( insufficient permissions, no index definition, no home page )
|
404
|
The requested page does not exist, ( What the client wants, not on the server )
|
500
|
Internal server error, (selinux,iptables, HTTP service not allowed, 500 error occurred )
|
502
|
Bad Gateway, HTTP back-end node request, no response ( you find intermediary, intermediary told you no room ) |
503
|
Service is currently unavailable,(server load is too large, service is abnormal, downtime maintenance, etc.)
|
504
|
When the network timeout, the server response time, reached beyond the set range ( you find intermediary, intermediary did not find the landlord, directly tell you no room )
|
To make it easy for everyone to save, upload a diagram
650) this.width=650; "src=" Https://s2.51cto.com/wyfs02/M02/93/0D/wKioL1kH36GDNn5zAAM-6hbOC30046.png "title=" 2_ copy. png "alt=" Wkiol1kh36gdnn5zaam-6hboc30046.png "/>
This article is from the "funny Brother Notes" blog, be sure to keep this source http://qiuyt.blog.51cto.com/1229789/1921045
Common error status codes for Web servers