The status code is a 3-digit number:

  • 1xx (Informational): Request received, server is continuing the process.
  • 2xx (Success): The request was successfully received, understood, accepted and serviced.
  • 3xx (Redirection): Further action must be taken in order to complete the request.
  • 4xx (Client Error): The request contains bad syntax or cannot be understood.
  • 5xx (Server Error): The server failed to fulfill an apparently valid request.

Some commonly encountered status codes are:

  • 100 Continue: The server received the request and in the process of giving the response.
  • 200 OK: The request is fulfilled.
  • 301 Move Permanently: The resource requested for has been permanently moved to a new location. The URL of the new location is given in the response header called Location. The client should issue a new request to the new location. Application should update all references to this new location.
  • 302 Found & Redirect (or Move Temporarily): Same as 301, but the new location is temporarily in nature. The client should issue a new request, but applications need not update the references.
  • 304 Not Modified: In response to the If-Modified-Since conditional GET request, the server notifies that the resource requested has not been modified.
  • 400 Bad Request: Server could not interpret or understand the request, probably syntax error in the request message.
  • 401 Authentication Required: The requested resource is protected, and require client’s credential (username/password). The client should re-submit the request with his credential (username/password).
  • 403 Forbidden: Server refuses to supply the resource, regardless of identity of client.
  • 404 Not Found: The requested resource cannot be found in the server.
  • 405 Method Not Allowed: The request method used, e.g., POST, PUT, DELETE, is a valid method. However, the server does not allow that method for the resource requested.
  • 408 Request Timeout:
  • 414 Request URI too Large:
  • 500 Internal Server Error: Server is confused, often caused by an error in the server-side program responding to the request.
  • 501 Method Not Implemented: The request method used is invalid (could be caused by a typing error, e.g., "GET" misspell as "Get").
  • 502 Bad Gateway: Proxy or Gateway indicates that it receives a bad response from the upstream server.
  • 503 Service Unavailable: Server cannot response due to overloading or maintenance. The client can try again later.
  • 504 Gateway Timeout: Proxy or Gateway indicates that it receives a timeout from an upstream server.

最新文章

  1. UGUI研究院之控件以及按钮的监听事件系统
  2. 如何使用Python在Kaggle竞赛中成为Top15
  3. LInux配置jdk(mac和windows)
  4. .NET 页面间传值的几种方法
  5. hdu 1016
  6. 【linux】——FreeBSD 建立 SSH 连接慢的解决方法
  7. Effective STL
  8. apache配置weblogic部署集群,多节点的项目和单节点项目并存 负载均衡
  9. 关于UNION ALL与 UNION 用法和区别
  10. MAC如何直接管理安卓手机文件(转)
  11. 综合查询员工和datetime.now和datetime.today区别
  12. C#管理控制IIS7的方法
  13. C++学习日记(二)————初始字符串类型
  14. Android利用ViewPager仿微信主界面-android学习之旅(78)
  15. Linux的内存分页管理
  16. 树莓派SSH连接快速教程
  17. windows10误删Administrator用户的家目录之后
  18. mysql常用命令行操作(二):表和库的操作、引擎、聚合函数
  19. [转]cubemap soft shadow
  20. windows 查看端口

热门文章

  1. Linux 下安装中文字体
  2. ESP8266的使用学习
  3. SpringBoot最新教程IDEA版【狂神说Java系列】
  4. dnsmasq+Stunnel+sniproxy加密代理
  5. B/S上传文件夹
  6. FLASH位宽为8、16、32时,CPU与外设之间地址线的连接方法
  7. RabbitMQ(Exchange交换机详解)(四)
  8. Collections 索引
  9. nodejs工作大全
  10. vue路由实例