HTTP 상태 코드
모든 HTTP 상태 코드를 카테고리별로 설명과 함께 검색하세요.
100
1xx
Continue
The server has received the request headers and the client should proceed to send the request body.
101
1xx
Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
200
2xx
OK
The request has succeeded.
201
2xx
Created
The request has succeeded and a new resource has been created as a result.
202
2xx
Accepted
The request has been received but not yet acted upon.
204
2xx
No Content
The server successfully processed the request but is not returning any content.
206
2xx
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
301
3xx
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
302
3xx
Found
Tells the client to look at another URL. Temporary redirect.
303
3xx
See Other
The response can be found under a different URL using the GET method.
304
3xx
Not Modified
The resource has not been modified since last request. Cached version is still valid.
307
3xx
Temporary Redirect
Redirect to another URL, preserving request method. Temporary.
308
3xx
Permanent Redirect
Permanent redirect that preserves the request method.
400
4xx
Bad Request
The server could not understand the request due to invalid syntax.
401
4xx
Unauthorized
Authentication is required and has failed or has not yet been provided.
403
4xx
Forbidden
The client does not have access rights to the content.
404
4xx
Not Found
The server can not find the requested resource.
405
4xx
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
408
4xx
Request Timeout
The server would like to shut down this unused connection.
409
4xx
Conflict
The request could not be completed due to a conflict with the current state of the resource.
410
4xx
Gone
Access to the target resource is no longer available and this condition is likely to be permanent.
413
4xx
Payload Too Large
The request entity is larger than the server is willing or able to process.
414
4xx
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
415
4xx
Unsupported Media Type
The media format of the request is not supported by the server.
422
4xx
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
429
4xx
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
500
5xx
Internal Server Error
The server has encountered a situation it does not know how to handle.
501
5xx
Not Implemented
The request method is not supported by the server and cannot be handled.
502
5xx
Bad Gateway
The server, while working as a gateway, received an invalid response from the upstream server.
503
5xx
Service Unavailable
The server is not ready to handle the request. Common causes: maintenance or overloaded.
504
5xx
Gateway Timeout
The server is acting as a gateway and cannot get a response in time.
505
5xx
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
이 도구 소개
HTTP 상태 코드 레퍼런스는 HTTP 프로토콜에 정의된 모든 주요 상태 코드를 카테고리별로 정리한 참조 도구입니다.
1xx(정보), 2xx(성공), 3xx(리다이렉션), 4xx(클라이언트 오류), 5xx(서버 오류) 5개 범주로 구성되며, 각 코드의 이름과 상세 설명을 제공합니다.
사용 방법
- 검색창에 코드 번호, 이름, 또는 설명 키워드를 입력하세요.
- 카테고리 필터로 특정 상태 코드 범주만 볼 수 있습니다.
- 코드 카드에서 상태 코드, 이름, 설명을 확인하세요.
- 필요한 코드를 찾아 API 개발이나 디버깅에 활용하세요.
활용 사례
API 개발 시 적절한 상태 코드 선택, 웹 서버 오류 디버깅, HTTP 프로토콜 학습, REST API 문서 작성 등에 활용하세요.
자주 묻는 질문
- 모든 HTTP 상태 코드가 포함되나요? — 네, RFC 7231 및 관련 표준에 정의된 주요 상태 코드를 모두 포함합니다.
- 4xx와 5xx 오류의 차이는 무엇인가요? — 4xx는 클라이언트 측 오류(잘못된 요청, 인증 실패 등)이고, 5xx는 서버 측 오류(서버 내부 오류, 과부하 등)입니다.
- 301과 302의 차이는 무엇인가요? — 301은 영구 리다이렉션(URL이 영구적으로 변경됨)이고, 302는 임시 리다이렉션입니다. SEO 측면에서 영구 이동에는 301을 사용하세요.