DevToolBox

HTTP Status Code Reference

HTTPステータスコードの一覧と検索。カテゴリ別に分類、番号や名前でフィルタリングできます。

広告スペース

1xx Informational

100
Continue

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

101
Switching Protocols

The server is switching protocols as requested by the client via the Upgrade header.

2xx Success

200
OK

The request has succeeded. The meaning depends on the HTTP method used.

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.

204
No Content

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

3xx Redirection

301
Moved Permanently

The requested resource has been permanently moved to a new URL.

302
Found

The requested resource temporarily resides under a different URL.

304
Not Modified

The resource has not been modified since the last request; use the cached version.

307
Temporary Redirect

The request should be repeated with another URL, but future requests should still use the original URL.

308
Permanent Redirect

The request and all future requests should be repeated using another URL, preserving the HTTP method.

4xx Client Error

400
Bad Request

The server cannot process the request due to a client error (e.g., malformed syntax).

401
Unauthorized

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

403
Forbidden

The server understood the request but refuses to authorize it.

404
Not Found

The requested resource could not be found on the server.

405
Method Not Allowed

The request method is not supported for the requested resource.

408
Request Timeout

The server timed out waiting for the request from the client.

409
Conflict

The request could not be completed due to a conflict with the current state of the resource.

410
Gone

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

413
Payload Too Large

The request entity 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 media format of the requested data is not supported by the server.

429
Too Many Requests

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

5xx Server Error

500
Internal Server Error

The server has encountered a situation it does not know how to handle.

501
Not Implemented

The request method is not supported by the server and cannot be handled.

502
Bad Gateway

The server received an invalid response from an upstream server.

503
Service Unavailable

The server is not ready to handle the request, often due to maintenance or overload.

504
Gateway Timeout

The server did not receive a timely response from an upstream server.

How to Use the HTTP Status Code Reference

This HTTP status code reference provides a comprehensive list of all common HTTP response status codes, organized by category. Use the search filter at the top to quickly find any status code by its number or name. The tool displays all codes from 1xx informational responses through 5xx server errors, with a clear description of each code meaning and typical use case. All data is displayed client-side with no server calls needed.

Understanding HTTP Status Code Categories

HTTP status codes are divided into five categories. 1xx codes are informational responses indicating the request was received and processing continues. 2xx codes indicate successful processing, with 200 OK being the most common. 3xx codes handle redirections, telling the client to look elsewhere for the resource. 4xx codes represent client errors where the request contains bad syntax or cannot be fulfilled. 5xx codes indicate server errors where the server failed to fulfill an apparently valid request.

Common Status Codes for Web Developers

The most frequently encountered status codes in web development include 200 (OK) for successful requests, 301 and 302 for redirects, 404 for missing resources, and 500 for server errors. Understanding these codes is essential for debugging API integrations, configuring web servers, and building robust error handling in web applications. The 429 status code is increasingly important for rate-limited APIs, while 401 and 403 are critical for authentication and authorization flows.

HTTPステータスコードリファレンスについて

主要なHTTPステータスコードをカテゴリ別に一覧表示し、番号や名前で即座に検索できるリファレンスツールです。1xx情報レスポンスから5xxサーバーエラーまで網羅しており、各コードの意味と用途を確認できます。API開発やWeb開発のデバッグに便利です。

広告スペース

開発をもっと効率的に

PR

広告スペース