Mã trạng thái HTTP
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The server agrees to switch to the protocol specified in the Upgrade header field.
Processing
The server has received and is processing the request but no response is available yet (WebDAV).
Early Hints
Used to return some response headers before the final HTTP message (RFC 8297).
OK
The request succeeded. The response body contains the requested data.
Created
The request succeeded and a new resource was created. Usually sent after POST or PUT.
Accepted
The request has been accepted for processing but processing has not been completed.
Non-Authoritative Information
The response metadata comes from a copy or transform of the origin server's 200 response.
No Content
The request succeeded but the response body is empty. Common after DELETE or PUT.
Reset Content
The server fulfilled the request and the user agent should reset the document view.
Partial Content
The server is delivering only part of the resource due to a Range header in the request.
Multi-Status
The response body is an XML message with multiple status codes (WebDAV).
Already Reported
Members of a DAV binding have already been enumerated in a previous reply (WebDAV).
IM Used
The server has fulfilled a GET request using delta encoding (RFC 3229).
Multiple Choices
The request has more than one possible response. The client should choose one.
Moved Permanently
The requested resource has been permanently moved to the URL in the Location header.
Found
The requested resource is temporarily at a different URL. Use 307 for method preservation.
See Other
The response to the request can be found at another URI using GET.
Not Modified
The cached version is still valid. No body is returned; the client should use its cache.
Use Proxy
Deprecated. The requested resource must be accessed through the proxy given by the Location field.
Temporary Redirect
The resource is temporarily at a different URL. The method and body must not be changed.
Permanent Redirect
The resource has permanently moved. Method and body must not change (unlike 301).
Bad Request
The server cannot process the request due to malformed syntax or invalid parameters.
Unauthorized
Authentication is required and has failed or has not yet been provided.
Payment Required
Reserved for future use; some services use it for quota exceeded or subscription required.
Forbidden
The server understood the request but refuses to authorize it. No authentication will help.
Not Found
The server cannot find the requested resource. The URL is not recognized.
Method Not Allowed
The request method is known but not supported by the target resource.
Not Acceptable
No content matching the Accept headers sent in the request was found.
Proxy Authentication Required
Authentication is required with a proxy before the request can be served.
Request Timeout
The server timed out waiting for the rest of the request from the client.
Conflict
The request conflicts with the current state of the resource (e.g., version conflict).
Gone
The resource was permanently deleted and will not be available again.
Length Required
The request did not include a Content-Length header field which the server requires.
Precondition Failed
One or more conditions given in the request header fields evaluated to false.
Content Too Large
The request body exceeds the server's maximum allowed size.
URI Too Long
The URI provided was too long for the server to process.
Unsupported Media Type
The request payload format is not supported by the server.
Range Not Satisfiable
The range specified in the Range header cannot be fulfilled.
Expectation Failed
The server cannot meet the expectation in the Expect request header field.
I'm a Teapot
A teapot is not a coffee machine (RFC 2324 / April Fools' joke — permanent in HTTP).
Misdirected Request
The request was directed at a server unable to produce a response for the host/port combination.
Unprocessable Content
The request is well-formed but contains semantic errors that prevent processing (WebDAV).
Locked
The source or destination resource of a method is locked (WebDAV).
Failed Dependency
The method could not be performed because the requested action depended on another action that failed (WebDAV).
Too Early
The server is unwilling to risk processing a request that might be replayed (RFC 8470).
Upgrade Required
The client should switch to a different protocol given in the Upgrade header field.
Precondition Required
The server requires the request to be conditional to prevent lost updates (RFC 6585).
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Request Header Fields Too Large
The server is unwilling to process the request because header fields are too large.
Unavailable For Legal Reasons
The resource is unavailable due to legal demands (e.g., censorship or court order).
Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
Not Implemented
The server does not support the functionality required to fulfill the request.
Bad Gateway
The server acting as a gateway received an invalid response from the upstream server.
Service Unavailable
The server is not ready to handle the request, usually due to maintenance or overload.
Gateway Timeout
The gateway server did not receive a timely response from the upstream server.
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
Variant Also Negotiates
The server has an internal configuration error with transparent content negotiation (RFC 2295).
Insufficient Storage
The server cannot store the representation needed to complete the request (WebDAV).
Loop Detected
The server detected an infinite loop while processing the request (WebDAV).
Not Extended
Further extensions to the request are required for the server to fulfill it (RFC 2774).
Network Authentication Required
The client must authenticate to gain network access (RFC 6585, e.g., captive portals).
Cách sử dụng Công cụ Mã trạng thái HTTP
Công cụ tra cứu mã trạng thái HTTP của BKNS rất đơn giản và trực quan. Bạn chỉ cần làm theo các bước sau:
- Nhập hoặc chọn mã: Gõ số mã trạng thái (ví dụ: 200, 404, 500) hoặc chọn từ danh sách các nhóm 1xx, 2xx, 3xx, 4xx, 5xx
- Xem chi tiết ngay lập tức: Công cụ sẽ hiển thị ý nghĩa chính xác, mô tả chi tiết và các trường hợp sử dụng phổ biến của mã
- Lọc theo nhóm: Sử dụng bộ lọc để xem tất cả mã trong một nhóm cụ thể (thông tin, thành công, chuyển hướng, lỗi client, lỗi server)
Khi nào cần dùng Mã trạng thái HTTP
Mã trạng thái HTTP rất hữu ích trong các tình huống sau:
- Phát triển web: Kiểm tra phản hồi từ API, debug lỗi kết nối và xác minh logic xử lý request
- SEO và kiểm tra website: Phát hiện lỗi 404, 500, kiểm tra chuyển hướng 301/302 và trạng thái máy chủ
- Quản lý máy chủ: Theo dõi và phân tích các mã trạng thái từ logs máy chủ web
- Hỗ trợ kỹ thuật: Giải thích nhanh cho khách hàng về các lỗi kết nối hay lỗi máy chủ
- Học tập và đào tạo: Tìm hiểu về giao thức HTTP theo chuẩn RFC 9110
NVMe Hosting tối ưu tốc độ — giúp website lên top Google
Giải thích kỹ thuật về Mã trạng thái HTTP
Mã trạng thái HTTP được định nghĩa trong chuẩn RFC 9110 và được chia thành 5 nhóm chính:
- Nhóm 1xx (Thông tin): Chỉ ra rằng yêu cầu đã được nhận và tiếp tục xử lý (ví dụ: 100 Continue, 101 Switching Protocols)
- Nhóm 2xx (Thành công): Yêu cầu đã được xử lý thành công (ví dụ: 200 OK, 201 Created, 204 No Content)
- Nhóm 3xx (Chuyển hướng): Cần thực hiện hành động bổ sung để hoàn thành yêu cầu (ví dụ: 301 Moved Permanently, 302 Found, 304 Not Modified)
- Nhóm 4xx (Lỗi client): Yêu cầu không hợp lệ hoặc không thể được xử lý (ví dụ: 400 Bad Request, 401 Unauthorized, 404 Not Found)
- Nhóm 5xx (Lỗi server): Máy chủ không thể xử lý yêu cầu hợp lệ (ví dụ: 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable)
Công cụ của BKNS chạy hoàn toàn trên trình duyệt của bạn, không cần gửi dữ liệu tới máy chủ, đảm bảo tốc độ nhanh và bảo mật.