HTTP 상태 코드 레퍼런스
설명, 사용 사례, 예시와 함께 HTTP 상태 코드를 조회합니다.
The server has received the request headers and the client should proceed to send the request body.
사용 사례: Used in POST requests with large bodies; client checks if server will accept before sending.
The server agrees to switch protocols as requested by the client.
사용 사례: WebSocket upgrade from HTTP to WS protocol.
The server has received and is processing the request, but no response is available yet.
사용 사례: Long-running operations to prevent client timeout.
Used to return some response headers before final HTTP message.
사용 사례: Preloading resources before the main response is ready.
The request succeeded. The meaning depends on the HTTP method used.
사용 사례: Standard success response for GET, POST, PUT requests.
The request succeeded and a new resource was created as a result.
사용 사례: Returned after a successful POST that creates a new resource.
The request has been accepted for processing, but processing has not been completed.
사용 사례: Async operations where processing happens in background.
The server successfully processed the request and is not returning any content.
사용 사례: DELETE requests, or PUT/PATCH with no response body needed.
The server is delivering only part of the resource due to a Range header sent by the client.
사용 사례: Video streaming, resumable file downloads.
The requested resource has been permanently moved to a new URL.
사용 사례: Permanent redirects; SEO-friendly for URL changes.
The resource is temporarily under a different URI.
사용 사례: Temporary redirects, login redirects.
The resource has not been modified since the last request.
사용 사례: Browser caching; server confirms cached version is still valid.
The request should be repeated with another URI but future requests can still use the original URI.
사용 사례: Temporary redirect that preserves the HTTP method.
The request and all future requests should be repeated using another URI.
사용 사례: Permanent redirect that preserves the HTTP method.
The server could not understand the request due to invalid syntax.
사용 사례: Malformed JSON, missing required fields, invalid parameters.
The client must authenticate itself to get the requested response.
사용 사례: Missing or invalid authentication token.
The client does not have access rights to the content.
사용 사례: Authenticated but not authorized; access denied to resource.
The server can not find the requested resource.
사용 사례: Invalid URL, deleted resource, or hidden resource.
The request method is known by the server but is not supported by the target resource.
사용 사례: POST to a read-only endpoint, DELETE on non-deletable resource.
The server would like to shut down this unused connection.
사용 사례: Client took too long to send a complete request.
The request conflicts with the current state of the server.
사용 사례: Duplicate resource creation, version conflicts.
The requested content has been permanently deleted from the server.
사용 사례: Deliberately removed resources; stronger signal than 404.
The request was well-formed but was unable to be followed due to semantic errors.
사용 사례: Validation errors — correct format but invalid data.
The user has sent too many requests in a given amount of time (rate limiting).
사용 사례: API rate limiting, DDoS protection.
The server encountered an unexpected condition that prevented it from fulfilling the request.
사용 사례: Unhandled exceptions, server-side bugs.
The server does not support the functionality required to fulfill the request.
사용 사례: HTTP method not recognized or supported by server.
The server, while acting as a gateway, received an invalid response from an upstream server.
사용 사례: Reverse proxy issues, upstream server errors.
The server is not ready to handle the request.
사용 사례: Server maintenance, overloaded server.
The server is acting as a gateway and cannot get a response in time.
사용 사례: Upstream server too slow, network timeouts.
The HTTP version used in the request is not supported by the server.
사용 사례: Client using unsupported HTTP version.
Comments & Feedback
Comments are powered by Giscus. Sign in with GitHub to leave a comment.