| 100 | Continue | 等待继续 | |
| 101 | Switching Protocols | 正在切换协议 | |
| 102 | Processing | 处理中 | |
| 103 | Early Hints | | |
| 200 | OK | 请求成功 | |
| 201 | Created | | |
| 202 | Accepted | | |
| 203 | Non-Authoritative Information | | |
| 204 | No Content | | |
| 205 | Reset Content | | |
| 206 | Partial Content | 只返回部分内容 | 当客户端发送Range报头时会响应206 |
| 300 | Multiple Choices | | |
| 301 | Moved Permanently | 永久移动到新的地址 | |
| 302 | Found | 暂时移动到新的地址 | |
| 303 | See Other | GET跳转 | |
| 304 | Not Modified | 响应内容无修改 | |
| 305 | Use Proxy | | |
| 307 | Temporary Redirect | 临时跳转 | |
| 308 | Permanent Redirect | 永久跳转 | |
| 400 | Bad Request | 客户端请求格式错误 | 很多Web服务也会把找不到域名响应为400 |
| 401 | Unauthorized | 客户端验证失败 | |
| 402 | Payment Required | | |
| 403 | Forbidden | 客户端被禁止访问 | |
| 404 | Not Found | 找不到客户端需要的资源 | |
| 405 | Method Not Allowed | 客户端的请求方法不被支持 | 比如有些服务的GET和POST不能混用，就会返回405 |
| 406 | Not Acceptable | | |
| 407 | Proxy Authentication Required | | |
| 408 | Request Timeout | 客户端发送的请求超时 | |
| 409 | Conflict | | |
| 410 | Gone | | |
| 411 | Length Required | 客户端发送的请求报头Content-Length未定义 | |
| 412 | Precondition Failed | | |
| 413 | Request Entity Too Large | 客户端发送的请求内容尺寸过大，超出服务器端限制 | |
| 414 | Request-URI Too Long | 客户端发送的请求URI长度过长，超出服务器端限制 | |
| 415 | Unsupported Media Type | | |
| 416 | Requested Range Not Satisfiable | | |
| 417 | Expectation Failed | | |
| 429 | Too Many Requests | 客户端发送的请求数过多 | 如果服务器端限制了请求速率，那么就有可能出现429 |
| 500 | Internal Server Error | | |
| 501 | Not Implemented | | |
| 502 | Bad Gateway | 服务器端处理请求时发送错误 | 通常是源站返回了错误的状态码或内容 |
| 503 | Service Unavailable | 服务器端无法处理 | 通常是配置错误导致服务器端无法处理或转发用户请求 |
| 504 | Gateway Timeout | 服务器端处理超时 | 通常是源站无法在有效时间内返回请求的内容 |
| 505 | HTTP Version Not Supported | 服务器端不支持当前请求的HTTP版本 | |
