HTTP Status Code Dictionary

Look up HTTP status codes and their meanings. Understand 404, 500, and other HTTP response codes with detailed explanations and solutions

βœ… Local ProcessingπŸ“‘ HTTP Reference
100Continue
Description:

ν΄λΌμ΄μ–ΈνŠΈκ°€ μš”μ²­μ„ 계속 μ§„ν–‰ν•  수 있음

Cause:

μ„œλ²„κ°€ μš”μ²­μ˜ 첫 뢀뢄을 λ°›μ•˜μŒ

Solution:

ν΄λΌμ΄μ–ΈνŠΈλŠ” μš”μ²­μ„ 계속 전솑

101Switching Protocols
Description:

ν”„λ‘œν† μ½œ μ „ν™˜ 쀑

Cause:

μ„œλ²„κ°€ ν΄λΌμ΄μ–ΈνŠΈμ˜ ν”„λ‘œν† μ½œ μ „ν™˜ μš”μ²­μ„ 승인

Solution:

μƒˆ ν”„λ‘œν† μ½œλ‘œ 톡신 계속

200OK
Description:

μš”μ²­ 성곡

Cause:

μ„œλ²„κ°€ μš”μ²­μ„ μ„±κ³΅μ μœΌλ‘œ 처리

Solution:

정상 응닡, μΆ”κ°€ 쑰치 λΆˆν•„μš”

201Created
Description:

λ¦¬μ†ŒμŠ€ 생성 성곡

Cause:

POST/PUT μš”μ²­μœΌλ‘œ μƒˆ λ¦¬μ†ŒμŠ€ 생성

Solution:

Location ν—€λ”λ‘œ λ¦¬μ†ŒμŠ€ μœ„μΉ˜ 확인

204No Content
Description:

μ„±κ³΅ν–ˆμ§€λ§Œ 응닡 λ³Έλ¬Έ μ—†μŒ

Cause:

μš”μ²­ 처리 성곡, λ°˜ν™˜ν•  데이터 μ—†μŒ

Solution:

정상, μΆ”κ°€ 쑰치 λΆˆν•„μš”

301Moved Permanently
Description:

λ¦¬μ†ŒμŠ€κ°€ 영ꡬ적으둜 이동

Cause:

URL이 영ꡬ적으둜 변경됨

Solution:

Location ν—€λ”μ˜ μƒˆ URL둜 이동, 뢁마크 μ—…λ°μ΄νŠΈ

302Found
Description:

λ¦¬μ†ŒμŠ€κ°€ μž„μ‹œλ‘œ 이동

Cause:

URL이 μΌμ‹œμ μœΌλ‘œ 변경됨

Solution:

Location ν—€λ”μ˜ URL둜 μž„μ‹œ 이동

304Not Modified
Description:

μΊμ‹œλœ λ¦¬μ†ŒμŠ€ μ‚¬μš© κ°€λŠ₯

Cause:

λ¦¬μ†ŒμŠ€κ°€ μˆ˜μ •λ˜μ§€ μ•ŠμŒ

Solution:

μΊμ‹œλœ 버전 μ‚¬μš©, μž¬λ‹€μš΄λ‘œλ“œ λΆˆν•„μš”

307Temporary Redirect
Description:

μž„μ‹œ λ¦¬λ‹€μ΄λ ‰νŠΈ (λ©”μ„œλ“œ μœ μ§€)

Cause:

λ¦¬μ†ŒμŠ€κ°€ μž„μ‹œλ‘œ λ‹€λ₯Έ URI에 μœ„μΉ˜

Solution:

Location ν—€λ”μ˜ URL둜 이동, μ›λž˜ HTTP λ©”μ„œλ“œ μœ μ§€

308Permanent Redirect
Description:

영ꡬ λ¦¬λ‹€μ΄λ ‰νŠΈ (λ©”μ„œλ“œ μœ μ§€)

Cause:

λ¦¬μ†ŒμŠ€κ°€ 영ꡬ적으둜 λ‹€λ₯Έ URI둜 이동

Solution:

Location ν—€λ”μ˜ URL둜 이동, HTTP λ©”μ„œλ“œ μœ μ§€

400Bad Request
Description:

잘λͺ»λœ μš”μ²­

Cause:

μš”μ²­ ꡬ문 였λ₯˜, 잘λͺ»λœ νŒŒλΌλ―Έν„°

Solution:

μš”μ²­ ν˜•μ‹ 확인, API λ¬Έμ„œ μ°Έκ³ 

401Unauthorized
Description:

인증 ν•„μš”

Cause:

인증 정보 μ—†μŒ λ˜λŠ” μœ νš¨ν•˜μ§€ μ•ŠμŒ

Solution:

μ˜¬λ°”λ₯Έ 인증 정보(토큰, λΉ„λ°€λ²ˆν˜Έ) 제곡

403Forbidden
Description:

μ ‘κ·Ό κ±°λΆ€

Cause:

κΆŒν•œ μ—†μŒ, 인증은 λ˜μ—ˆμœΌλ‚˜ ν—ˆκ°€λ˜μ§€ μ•ŠμŒ

Solution:

μ ‘κ·Ό κΆŒν•œ 확인, κ΄€λ¦¬μžμ—κ²Œ κΆŒν•œ μš”μ²­

404Not Found
Description:

λ¦¬μ†ŒμŠ€λ₯Ό 찾을 수 μ—†μŒ

Cause:

URL μ˜€νƒ€, μ‚­μ œλœ λ¦¬μ†ŒμŠ€

Solution:

URL 확인, λ¦¬μ†ŒμŠ€ 쑴재 μ—¬λΆ€ 확인

405Method Not Allowed
Description:

ν—ˆμš©λ˜μ§€ μ•ŠλŠ” HTTP λ©”μ„œλ“œ

Cause:

GET μš”μ²­λ§Œ ν—ˆμš©ν•˜λŠ”λ° POST 전솑 λ“±

Solution:

ν—ˆμš©λœ HTTP λ©”μ„œλ“œ 확인 (Allow 헀더)

408Request Timeout
Description:

μš”μ²­ μ‹œκ°„ 초과

Cause:

μ„œλ²„κ°€ μš”μ²­μ„ κΈ°λ‹€λ¦¬λŠ” λ™μ•ˆ μ‹œκ°„ 초과

Solution:

λ„€νŠΈμ›Œν¬ μƒνƒœ 확인, μž¬μ‹œλ„

409Conflict
Description:

λ¦¬μ†ŒμŠ€ 좩돌

Cause:

쀑볡 데이터, 버전 좩돌

Solution:

ν˜„μž¬ μƒνƒœ 확인 ν›„ μž¬μ‹œλ„

413Payload Too Large
Description:

μš”μ²­ νŽ˜μ΄λ‘œλ“œκ°€ λ„ˆλ¬΄ 큼

Cause:

μ—…λ‘œλ“œ 파일 크기 μ œν•œ 초과

Solution:

파일 크기 쀄이기, μ„œλ²„ μ œν•œ 확인

414URI Too Long
Description:

URL이 λ„ˆλ¬΄ κΉ€

Cause:

GET μš”μ²­μ˜ 쿼리 νŒŒλΌλ―Έν„°κ°€ λ„ˆλ¬΄ 많음

Solution:

POST둜 λ³€κ²½, URL 길이 쀄이기

415Unsupported Media Type
Description:

μ§€μ›ν•˜μ§€ μ•ŠλŠ” λ―Έλ””μ–΄ νƒ€μž…

Cause:

Content-Type이 잘λͺ»λ¨

Solution:

μ˜¬λ°”λ₯Έ Content-Type 헀더 μ„€μ •

429Too Many Requests
Description:

μš”μ²­ 횟수 μ œν•œ 초과

Cause:

Rate Limit 초과

Solution:

일정 μ‹œκ°„ ν›„ μž¬μ‹œλ„, Retry-After 헀더 확인

500Internal Server Error
Description:

μ„œλ²„ λ‚΄λΆ€ 였λ₯˜

Cause:

μ„œλ²„ μ½”λ“œ 였λ₯˜, μ˜ˆμ™Έ λ°œμƒ

Solution:

μ„œλ²„ 둜그 확인, κ΄€λ¦¬μžμ—κ²Œ 문의

501Not Implemented
Description:

κ΅¬ν˜„λ˜μ§€ μ•Šμ€ κΈ°λŠ₯

Cause:

μ„œλ²„κ°€ μš”μ²­ λ©”μ„œλ“œλ₯Ό μ§€μ›ν•˜μ§€ μ•ŠμŒ

Solution:

μ„œλ²„ κΈ°λŠ₯ 확인, API λ¬Έμ„œ μ°Έκ³ 

502Bad Gateway
Description:

κ²Œμ΄νŠΈμ›¨μ΄ 였λ₯˜

Cause:

κ²Œμ΄νŠΈμ›¨μ΄/ν”„λ‘μ‹œ μ„œλ²„κ°€ 잘λͺ»λœ 응닡 λ°›μŒ

Solution:

μž μ‹œ ν›„ μž¬μ‹œλ„, μ„œλ²„ μƒνƒœ 확인

503Service Unavailable
Description:

μ„œλΉ„μŠ€ 이용 λΆˆκ°€

Cause:

μ„œλ²„ κ³ΌλΆ€ν•˜, μœ μ§€λ³΄μˆ˜ 쀑

Solution:

Retry-After 헀더 확인 ν›„ μž¬μ‹œλ„

504Gateway Timeout
Description:

κ²Œμ΄νŠΈμ›¨μ΄ μ‹œκ°„ 초과

Cause:

μ—…μŠ€νŠΈλ¦Ό μ„œλ²„ 응닡 μ—†μŒ

Solution:

μž¬μ‹œλ„, νƒ€μž„μ•„μ›ƒ μ„€μ • 확인

505HTTP Version Not Supported
Description:

HTTP 버전 미지원

Cause:

μ„œλ²„κ°€ μš”μ²­μ˜ HTTP 버전을 μ§€μ›ν•˜μ§€ μ•ŠμŒ

Solution:

HTTP 버전 확인, μ„œλ²„ μ—…κ·Έλ ˆμ΄λ“œ

HTTP Status Codes FAQ and Reference

What is an HTTP status code?

HTTP status codes are 3-digit numbers that indicate the status of a web server's response to a client's request. Each code tells you whether the request succeeded, failed, or requires additional action.

Status Code Categories

  • 1xx (Informational): Request received, continuing process
  • 2xx (Success): Request successfully received, understood, and accepted
  • 3xx (Redirection): Further action needed to complete the request
  • 4xx (Client Error): Request contains an error and cannot be fulfilled
  • 5xx (Server Error): Server failed to fulfill a valid request

Most Common Error Codes

  • 404 Not Found: Most common error, page cannot be found
  • 500 Internal Server Error: Server internal error
  • 502 Bad Gateway: Gateway or proxy server received an invalid response
  • 503 Service Unavailable: Server temporarily cannot handle the request

Difference between 4xx and 5xx errors

4xx errors are client-side issues. Wrong URL, unauthorized access, bad request, etc. These are problems the client needs to fix.

5xx errors are server-side issues. Server down, code errors, gateway problems, etc. These are problems the server administrator needs to resolve.

How to resolve Rate Limit (429) errors

429 Too Many Requests occurs when you've sent too many requests.

  • Check the Retry-After header for when to retry
  • Reduce request frequency or use backoff strategy
  • Check API provider's rate limit policy

How to use this tool?

Search by status code number or name, or click category buttons to view specific ranges of codes. You can see the description, cause, and solution for each code.