HTTP 상태 코드

설명이 포함된 완전한 HTTP 상태 코드 레퍼런스.

50 개 상태 코드

100

Continue

The server has received the request headers and the client should proceed to send the request body.

101

Switching Protocols

The requester has asked the server to switch protocols and the server has agreed to do so.

102

Processing

The server has received and is processing the request, but no response is available yet.

103

Early Hints

Used to return some response headers before final HTTP message.

200

The request has succeeded. The meaning of the success depends on the HTTP method.

201

Created

The request has been fulfilled, resulting in the creation of a new resource.

202

Accepted

The request has been accepted for processing, but the processing has not been completed.

203

Non-Authoritative Information

The server is a transforming proxy that received a 200 OK from its origin.

204

No Content

The server successfully processed the request and is not returning any content.

205

Reset Content

The server successfully processed the request, asks the requester to reset its document view.

206

Partial Content

The server is delivering only part of the resource due to a range header sent by the client.

207

Multi-Status

The message body contains multiple separate response codes.

208

Already Reported

The members of a DAV binding have already been enumerated in a previous reply.

226

IM Used

The server has fulfilled a request for the resource, and the response represents instance-manipulations.

300

Multiple Choices

Indicates multiple options for the resource from which the client may choose.

301

Moved Permanently

This and all future requests should be directed to the given URI.

302

Found

Tells the client to look at another URL. Previously "Moved Temporarily".

303

See Other

The response to the request can be found under another URI using the GET method.

304

Not Modified

Indicates that the resource has not been modified since the version specified by the request headers.

307

Temporary Redirect

The request should be repeated with another URI; however, future requests should still use the original URI.

308

Permanent Redirect

The request and all future requests should be repeated using another URI.

400

Bad Request

The server cannot or will not process the request due to an apparent client error.

401

Unauthorized

Authentication is required and has failed or has not yet been provided.

402

Payment Required

Reserved for future use. The original intention was for digital payment schemes.

403

Forbidden

The request was valid, but the server is refusing action. The user might not have permissions.

404

Not Found

The requested resource could not be found but may be available in the future.

405

Method Not Allowed

A request method is not supported for the requested resource.

406

Not Acceptable

The requested resource is capable of generating only content not acceptable per Accept headers.

407

Proxy Authentication Required

The client must first authenticate itself with the proxy.

408

Request Timeout

The server timed out waiting for the request.

409

Conflict

The request could not be processed because of conflict in the current state of the resource.

410

Gone

The resource requested is no longer available and will not be available again.

411

Length Required

The request did not specify the length of its content, which is required by the resource.

412

Precondition Failed

The server does not meet one of the preconditions that the requester put on the request header.

413

Payload Too Large

The request is larger than the server is willing or able to process.

414

URI Too Long

The URI provided was too long for the server to process.

415

Unsupported Media Type

The request entity has a media type which the server does not support.

416

Range Not Satisfiable

The client has asked for a portion of the file that the server cannot supply.

418

I'm a Teapot

The server refuses the attempt to brew coffee with a teapot. (April Fools RFC 2324)

422

Unprocessable Entity

The request was well-formed but was unable to be followed due to semantic errors.

429

Too Many Requests

The user has sent too many requests in a given amount of time (rate limiting).

451

Unavailable For Legal Reasons

A server operator has received a legal demand to deny access to a resource.

500

Internal Server Error

A generic error message when an unexpected condition was encountered.

501

Not Implemented

The server does not recognize the request method, or it lacks the ability to fulfill the request.

502

Bad Gateway

The server was acting as a gateway and received an invalid response from the upstream server.

503

Service Unavailable

The server cannot handle the request (overloaded or down for maintenance).

504

Gateway Timeout

The server was acting as a gateway and did not receive a timely response from the upstream server.

505

HTTP Version Not Supported

The server does not support the HTTP protocol version used in the request.

507

Insufficient Storage

The server is unable to store the representation needed to complete the request.

511

Network Authentication Required

The client needs to authenticate to gain network access.

HTTP 상태 코드에 대하여

HTTP 상태 코드는 웹 서버가 반환하는 표준화된 응답 코드입니다. 특정 HTTP 요청이 성공적으로 완료되었는지 여부를 나타냅니다. 이 코드를 이해하는 것은 웹 개발, API 통합, 디버깅에 필수적입니다. 가장 자주 접하는 코드에는 200(OK), 301(영구 이동), 404(찾을 수 없음), 500(내부 서버 오류)이 있습니다.

자주 묻는 질문

HTTP 상태 코드란 무엇인가요?▾

HTTP 상태 코드는 웹 서버가 클라이언트의 요청 결과를 나타내기 위해 반환하는 3자리 숫자입니다. 1xx(정보), 2xx(성공), 3xx(리다이렉트), 4xx(클라이언트 오류), 5xx(서버 오류) 5개 그룹으로 나뉩니다.

404 오류는 무엇을 의미하나요?▾

404 Not Found는 서버가 요청된 리소스를 찾을 수 없음을 의미합니다. URL이 잘못 입력되었거나, 페이지가 삭제되었거나, 링크가 깨졌을 때 발생합니다.

301과 302 리다이렉트의 차이는 무엇인가요?▾

301(영구 이동)은 리소스가 새 URL로 영구적으로 이동했음을 의미합니다. 302(임시 이동)는 원래 URL을 계속 사용해야 하는 임시 리다이렉트입니다.

HTTP 상태 코드

HTTP 상태 코드에 대하여

관련 도구

자주 묻는 질문