100Information
Continue
The request headers arrived; the client may continue sending the request body.
Use when: Useful for streaming or large uploads.
HTTP REFERENCE
올바른 HTTP 상태 코드를 찾으세요
HTTP 상태 코드를 검색하고 응답의 의미와 사용 시점을 이해한 뒤 바로 쓸 상태 문구를 복사하세요.
* 모든 처리는 브라우저에서 진행됩니다. URL을 요청하지 않으며 입력값이 페이지 밖으로 나가지 않습니다.
23 개 코드
101Information
Switching Protocols
The server agrees to change protocols requested by the client.
Use when: Commonly used to establish a WebSocket connection.
200Success
OK
The request succeeded.
Use when: Use for a successful read or an action with a response body.
201Success
Created
The request succeeded and created a new resource.
Use when: Return after a successful POST, usually with a Location header.
202Success
Accepted
The request was accepted for processing, but processing is not complete.
Use when: Use for queued or asynchronous work.
204Success
No Content
The request succeeded and there is no response body to return.
Use when: Useful after DELETE or an update that needs no representation.
301Redirection
Moved Permanently
The resource has a new permanent URL.
Use when: Use when a URL should be replaced and search engines should update their links.
302Redirection
Found
The resource is temporarily available at another URL.
Use when: Use for a temporary redirect; preserve the original URL for future requests.
304Redirection
Not Modified
The cached representation is still fresh.
Use when: Return for a conditional request when the resource has not changed.
307Redirection
Temporary Redirect
The resource is temporarily available at another URL and the method must remain unchanged.
Use when: Use when a POST or other method must not be changed to GET.
308Redirection
Permanent Redirect
The resource has a new permanent URL and the method must remain unchanged.
Use when: Use for a permanent method-preserving redirect.
400Client error
Bad Request
The server cannot process the request because it is malformed or invalid.
Use when: Check syntax, required fields, and request parsing.
401Client error
Unauthorized
The request lacks valid authentication credentials.
Use when: The client should authenticate or refresh its credentials.
403Client error
Forbidden
The server understood the request but refuses to fulfill it.
Use when: Authentication may be present, but permission is missing.
404Client error
Not Found
The server cannot find the requested resource.
Use when: Check the URL, route, identifier, or whether the resource was removed.
405Client error
Method Not Allowed
The resource exists but does not support this request method.
Use when: Check the Allow header and the endpoint contract.
409Client error
Conflict
The request conflicts with the current state of the resource.
Use when: Resolve a version, uniqueness, or state conflict before retrying.
422Client error
Unprocessable Content
The request syntax is valid, but its instructions cannot be processed.
Use when: Return field or business-rule validation errors.
429Client error
Too Many Requests
The client sent too many requests in a given period.
Use when: Back off, respect Retry-After, and apply client-side rate limits.
500Server error
Internal Server Error
The server encountered an unexpected condition.
Use when: Inspect server logs and return a safe error body.
502Server error
Bad Gateway
A gateway received an invalid response from an upstream server.
Use when: Check the proxy, upstream health, and timeout behavior.
503Server error
Service Unavailable
The server is not ready to handle the request.
Use when: Use during overload or maintenance and include Retry-After when useful.
504Server error
Gateway Timeout
A gateway did not receive a timely response from an upstream server.
Use when: Check upstream latency, connection limits, and timeout settings.
QUICK GUIDE
의미에 맞는 응답을 선택하세요
서버가 요청을 완료했으면 2xx를 사용합니다.
다른 위치나 캐시를 사용해야 하면 3xx를 사용합니다.
요청을 받은 그대로 처리할 수 없으면 4xx를 사용합니다.
서버나 상위 의존성이 실패했으면 5xx를 사용합니다.
FAQ
HTTP 상태 코드 질문
What is the difference between 401 and 403?
401 means valid authentication is missing. 403 means the server knows who the client is but will not allow the action.
When should I use 422 instead of 400?
Use 400 for a malformed request. Use 422 when the request is well-formed but fails validation or a business rule.
Why use 307 or 308?
They preserve the original request method during a redirect, which matters for POST, PUT, and other non-GET requests.