Tra cứu Mã trạng thái HTTP (HTTP Status Codes)
Tra cứu ý nghĩa đầy đủ của tất cả mã trạng thái HTTP từ 1xx đến 5xx, bao gồm mô tả chi tiết và cách xử lý.
The server has received the request headers and the client should proceed to send the request body.
The server has received the request headers and the client should proceed to send the request body.
Used when the client sends large data and wants to check if the server will accept the request before the actual upload.
The requester has asked the server to switch protocols and the server has agreed to do so.
The requester has asked the server to switch protocols and the server has agreed to do so.
Commonly seen when establishing WebSockets connection from regular HTTP protocol.
Standard response for successful HTTP requests.
Standard response for successful HTTP requests.
Webpage displays successfully, API returns standard data.
The request has been fulfilled, resulting in the creation of a new resource.
The request has been fulfilled, resulting in the creation of a new resource.
Successful registration of a new account, creating a new record in database via POST method.
The request has been accepted for processing, but the processing has not been completed.
The request has been accepted for processing, but the processing has not been completed.
Submitting video rendering request, running heavy background tasks queuing for long processing times.
The server successfully processed the request, and is not returning any content.
The server successfully processed the request, and is not returning any content.
Successful DELETE request to remove resources, or auto-saving drafts.
The server is delivering only part of the resource due to a range header sent by the client.
The server is delivering only part of the resource due to a range header sent by the client.
Resuming file download, fast-forwarding streaming video on a browser.
This and all future requests should be directed to the given URI.
This and all future requests should be directed to the given URI.
Changing website domain name, redirecting all traffic from HTTP to HTTPS.
Tells the client to look at another URL, but future requests should still use the original URL.
Tells the client to look at another URL, but future requests should still use the original URL.
Redirecting unauthenticated users to login page, then back to the original page.
Indicates that the resource has not been modified since the version specified by the request headers.
Indicates that the resource has not been modified since the version specified by the request headers.
Reloading web page, browser uses cached images and CSS files to save bandwidth.
The request should be repeated with another URI; however, future requests should still use the original URI.
The request should be repeated with another URI; however, future requests should still use the original URI.
Temporarily redirecting POST request to another server while keeping the request body data intact.
The request and all future requests should be directed to another URI, keeping the method.
The request and all future requests should be directed to another URI, keeping the method.
Permanently redirecting API POST request to a new endpoint version (v1 -> v2).
The server cannot or will not process the request due to an apparent client error.
The server cannot or will not process the request due to an apparent client error.
Sending malformed JSON strings, missing required parameters in API request.
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed.
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed.
Accessing API requiring authentication without sending JWT Token in Authorization header.
The request was valid, but the server is refusing action. The user might not have the necessary permissions.
The request was valid, but the server is refusing action. The user might not have the necessary permissions.
Standard account attempting to access Admin management page.
The requested resource could not be found but may be available in the future.
The requested resource could not be found but may be available in the future.
User typo in URL path, or article deleted from system by admin.
A request method is not supported for the requested resource.
A request method is not supported for the requested resource.
Attempting POST request to a static HTML page that only allows GET.
The server timed out waiting for the request.
The server timed out waiting for the request.
Client network connection too weak, packet transmission interrupted midway.
Indicates that the request could not be processed because of conflict in the current state of the resource.
Indicates that the request could not be processed because of conflict in the current state of the resource.
Registering account with an email already existing in database.
The user has sent too many requests in a given amount of time (rate limiting).
The user has sent too many requests in a given amount of time (rate limiting).
Brute-forcing password, continuously spamming API in a short time.
A generic error message, given when an unexpected condition was encountered.
A generic error message, given when an unexpected condition was encountered.
Developer coding error (e.g. null pointer, division by zero) causing Node.js/PHP application crash.
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
Sending advanced API request not yet programmed in current server version.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Node.js app running under PM2 stopped/crashed, causing Nginx proxy to return 502 error to browser.
The server cannot handle the request (because it is overloaded or down for maintenance).
The server cannot handle the request (because it is overloaded or down for maintenance).
Ticketing website overloaded during hot event ticket sales, or server undergoing maintenance upgrade.
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
Database server processing SQL query too slowly (timeout), causing Gateway to disconnect first.