HTTPQUERY
中文

HTTP Status Codes

Browse status codes by category. Expand any row to see a real HTTP message example for that code.

1xxInformational

100ContinueThe client should continue sending the request body.Example
→ REQUEST
POST /uploads HTTP/1.1
Host: example.com
Content-Length: 5242880
Expect: 100-continue
← RESPONSE
HTTP/1.1 100 Continue

(client now streams the 5 MB body)

HTTP/1.1 201 Created
Location: /uploads/8f2c
In-depth page →
101Switching ProtocolsThe server agrees to switch protocols (e.g. upgrade to WebSocket).Example
→ REQUEST
GET /chat HTTP/1.1
Host: example.com
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==
Sec-WebSocket-Version: 13
← RESPONSE
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=
In-depth page →
102ProcessingUnderstand the 102 Processing status code, how the response prevents client timeouts during long-running requests, and its WebDAV origins.Example
→ REQUEST
GET /sample.pdf HTTP/1.1
Host: example.com
In-depth page →
103Early HintsUnderstand 103 Early Hints and how the status code speeds up page loads by preloading resources before the final response arrives.Example
→ REQUEST
GET /index.html HTTP/1.1
Host: example.com
In-depth page →

2xxSuccess

200OKThe request succeeded; the response contains the requested resource.Example
→ REQUEST
GET /products/42 HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 51

{ "id": 42, "name": "Trailhead Boot", "price": 189 }
In-depth page →
201CreatedThe request succeeded and a new resource was created.Example
→ REQUEST
POST /products HTTP/1.1
Host: example.com
Content-Type: application/json

{ "name": "Ridge Boot", "price": 210 }
← RESPONSE
HTTP/1.1 201 Created
Location: /products/43
Content-Type: application/json

{ "id": 43, "name": "Ridge Boot", "price": 210 }
In-depth page →
202AcceptedLearn what a 202 Accepted response means, how the status code signals asynchronous processing, and how to poll for the eventual result.Example
→ REQUEST
POST /job HTTP/1.1
Host: example.com
Content-Type: application/xml
Content-Length: 68

<?xml version="1.0"?>
<job>
  <id>125</id>
  <task>G01</task>
</job>
In-depth page →
203Non-Authoritative InformationLearn what a 203 Non-Authoritative Information response means, when proxies return 203, and how the status code differs from 200 OK.Example
→ REQUEST
GET /instructions HTTP/1.1
Host: example.com
In-depth page →
204No ContentSucceeded, with no response body.Example
→ REQUEST
DELETE /products/43 HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 204 No Content

(no body)
In-depth page →
205Reset ContentLearn what a 205 Reset Content response means, how the status code instructs clients to clear form data, and how 205 differs from 204.Example
→ REQUEST
POST /signup HTTP/1.1
Host: example.com
Content-Type: application/xml
Content-Length: 92

<?xml version="1.0"?>
<person>
  <name>David Smith</name>
  <country>USA</country>
</person>
In-depth page →
206Partial ContentUnderstand the 206 Partial Content response, how Range requests work for resumable downloads, and multipart range responses.Example
→ REQUEST
GET /videos/sample.mp4 HTTP/1.1
Host: example.com
Range: bytes=25000-75000
In-depth page →
207Multi-StatusLearn what a 207 Multi-Status response means, how WebDAV uses 207 to report per-resource results, and how to parse the XML body.Example
<d:response>
  <d:href>http://example.re/tasks</d:href>
  <d:status>HTTP/1.1 200 OK</d:status>
</d:response>
In-depth page →
208Already ReportedUnderstand the 208 Already Reported status code, how WebDAV uses 208 inside 207 responses to avoid duplicate resource listings.Example
→ REQUEST
PROPFIND /main/ HTTP/1.1
Host: example.com
Depth: infinity
DAV: bind
Content-Type: application/xml; charset="utf-8"
Content-Length: 139

<?xml version="1.0" encoding="utf-8" ?>
<d:propfind xmlns:d="DAV:">
  <d:prop>
    <d:name/>
    <d:link/>
  </d:prop>
</d:propfind>
In-depth page →
226IM UsedLearn what a 226 IM Used response means, how delta encoding and instance manipulations conserve bandwidth in HTTP responses.Example
→ REQUEST
GET /livingdocs/current_specs.pdf HTTP/1.1
Host: example.com
Accept-Encoding: gzip
In-depth page →

3xxRedirection

300Multiple ChoicesUnderstand the 300 Multiple Choices response, when servers send 300, and how clients select from multiple available representations.Example
→ REQUEST
GET /tech-news HTTP/1.1
Host: example.com
In-depth page →
301Moved PermanentlyThe resource has permanently moved to the address in Location.Example
→ REQUEST
GET /old-path HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 301 Moved Permanently
Location: https://example.com/new-path
In-depth page →
302FoundThe resource is temporarily at Location.Example
→ REQUEST
GET /account HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 302 Found
Location: /login
In-depth page →
303See OtherLearn how the 303 See Other redirect works, why 303 always switches to GET, and when to use 303 after POST, PUT, or DELETE requests.Example
→ REQUEST
DELETE /tasks/314 HTTP/1.1
Host: example.com
In-depth page →
304Not ModifiedThe cache is valid; the local copy can be used directly.Example
→ REQUEST
GET /logo.png HTTP/1.1
Host: example.com
If-None-Match: "9c2e-abc123"
← RESPONSE
HTTP/1.1 304 Not Modified
ETag: "9c2e-abc123"

(no body — reuse the cached copy)
In-depth page →
305Use ProxyLearn about the deprecated 305 Use Proxy status code, why 305 was removed over security concerns, and what replaced the status code.Example
→ REQUEST
GET /document.pdf HTTP/1.1
Host: example.com
In-depth page →
307Temporary RedirectUnderstand the 307 Temporary Redirect, why 307 preserves the request method unlike 302, and when to use 307 over 302 or 303.Example
→ REQUEST
GET /news.html HTTP/1.1
Host: example.com
In-depth page →
308Permanent RedirectUnderstand the 308 Permanent Redirect, how 308 preserves the request method unlike 301, and how search engines transfer link equity.Example
→ REQUEST
POST /api/v1/orders HTTP/1.1
Host: example.com
Content-Type: application/json
Content-Length: 35

{"item": "widget", "quantity": 10}
In-depth page →

4xxClient Error

400Bad RequestThe request syntax or parameters are invalid.Example
→ REQUEST
POST /products HTTP/1.1
Host: example.com
Content-Type: application/json

{ "price": "not-a-number" }
← RESPONSE
HTTP/1.1 400 Bad Request
Content-Type: application/json

{ "error": "price must be a number" }
In-depth page →
401UnauthorizedAuthentication is required.Example
→ REQUEST
GET /account HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer realm="api"
In-depth page →
402Payment RequiredUnderstand 402 Payment Required: a reserved status code, its non-standard usage by Shopify and Stripe, and SEO impact.Example
→ REQUEST
GET /tech-news HTTP/1.1
Host: example.com
In-depth page →
403ForbiddenAuthenticated but not authorized.Example
→ REQUEST
DELETE /users/1 HTTP/1.1
Host: example.com
Authorization: Bearer <valid-token>
← RESPONSE
HTTP/1.1 403 Forbidden
Content-Type: application/json

{ "error": "admin role required" }
In-depth page →
404Not FoundThe target resource was not found.Example
→ REQUEST
GET /products/9999 HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 404 Not Found
Content-Type: application/json

{ "error": "product 9999 not found" }
In-depth page →
405Method Not AllowedThe method is not allowed for this resource.Example
→ REQUEST
DELETE /products HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 405 Method Not Allowed
Allow: GET, POST, QUERY
In-depth page →
406Not AcceptableFix 406 Not Acceptable errors. Understand content negotiation, Accept headers, and how servers handle unsatisfiable requests.Example
Accept: text/html, text/plain
In-depth page →
407Proxy Authentication RequiredFix 407 Proxy Authentication Required errors. Learn proxy authentication schemes and Proxy-Authenticate headers.Example
→ REQUEST
GET /documents/tech-news HTTP/1.1
Host: example.com
In-depth page →
408Request TimeoutFix 408 Request Timeout errors. Understand why servers close slow connections and how to resolve transmission issues.Example
→ REQUEST
PUT /docs HTTP/1.1
Host: example.com
Content-Type: application/pdf
Content-Length: 10000
In-depth page →
409ConflictFix 409 Conflict errors. Understand resource state conflicts, resolution strategies, and common API use cases.Example
→ REQUEST
POST /blog/update?postid=111&flag=like HTTP/1.1
Host: example.com
In-depth page →
410GoneUnderstand 410 Gone: permanent resource removal, differences from 404, caching behavior, and SEO indexing impact.Example
→ REQUEST
GET /holiday-promotion-Jan-2021.pdf HTTP/1.1
Host: example.com
In-depth page →
411Length RequiredFix 411 Length Required errors. Learn when the Content-Length header is needed and how to resolve this client error.Example
→ REQUEST
PUT /docs HTTP/1.1
Host: example.com
Content-Type: application/pdf

<PDF file included as message body>
In-depth page →
412Precondition FailedFix 412 Precondition Failed errors. Learn conditional request headers, If-Match failures, and lost update prevention.Example
→ REQUEST
POST /blog/update?postid=111&task=reply HTTP/1.1
Host: example.com
If-Unmodified-Since: Fri, 1 Jan 2021 00:00:00 GMT
Content-Type: text/plain
Content-Length: 45

<Message body contains reply-text from the client>
In-depth page →
413Content Too LargeFix 413 Content Too Large errors. Learn server size limits, Expect header usage, and how to handle oversized uploads.Example
→ REQUEST
PUT /docs HTTP/1.1
Host: example.com
Content-Type: application/pdf
Content-Length: 10000
In-depth page →
414URI Too LongFix 414 URI Too Long errors. Understand URL length limits, browser restrictions, and how to shorten request URIs.Example
→ REQUEST
GET /<...a_long_URI...> HTTP/1.1
Host: example.com
In-depth page →
415Unsupported Media TypeFix 415 Unsupported Media Type errors. Learn Content-Type and Content-Encoding validation, with troubleshooting steps.Example
→ REQUEST
POST /blog/newmessage HTTP/1.1
Host: example.com
Content-Type: text/plain
Content-Length: 24

Good morning, Everybody!
In-depth page →
416Range Not SatisfiableFix 416 Range Not Satisfiable errors. Understand byte range requests, the Content-Range header, and resolution.Example
Content-Range: bytes */512
In-depth page →
417Expectation FailedFix 417 Expectation Failed errors. Learn how the Expect header and 100-continue mechanism work and when 417 is returned.Example
→ REQUEST
PUT /docs HTTP/1.1
Host: example.com
Content-Type: application/pdf
Content-Length: 10000
Expect: 100-continue
In-depth page →
418I'm a teapotI'm a teapot — the RFC 2324 easter-egg status code.Example
→ REQUEST
BREW /coffee HTTP/1.1
Host: teapot.example
← RESPONSE
HTTP/1.1 418 I'm a teapot
Content-Type: text/plain

I refuse to brew coffee — I am a teapot.
In-depth page →
421Misdirected RequestFix 421 Misdirected Request errors. Understand connection reuse, HTTP/2 routing, and Alt-Svc troubleshooting.Example
→ REQUEST
GET /tech-news HTTP/2
Host: example.com
In-depth page →
422Unprocessable ContentFix 422 Unprocessable Content errors. Learn differences from 400 and 415, and how to resolve semantic validation failures.Example
→ REQUEST
POST /requests HTTP/1.1
Host: example.com
Content-Type: application/xml
Content-Length: 101

<?xml version="1.0" encoding="utf-8"?>
<request>
   <id>100</id>
   <action>start</action>
</request>
In-depth page →
423LockedFix 423 Locked errors. Learn WebDAV file locking mechanisms, Lock-Token headers, precondition codes, and how to unlock resources.Example
→ REQUEST
PUT /documents/ HTTP/1.1
Host: example.com
Content-Type: application/pdf
Content-Length: 10000

<PDF file transferred>
In-depth page →
424Failed DependencyFix 424 Failed Dependency errors. Learn WebDAV multi-status responses, PROPPATCH operations, and dependency resolution.Example
→ REQUEST
PROPPATCH /update.html HTTP/1.1
Host: example.com
Content-Type: application/xml; charset="utf-8"
Content-Length: 305

<?xml version="1.0" encoding="utf-8" ?>
<d:propertyupdate xmlns:d="DAV:"
                  xmlns:z="urn:example">
  <d:set>
    <d:prop>
      <z:seats>
        <z:seatnumber>100</z:seatnumber>
        <z:seatnumber>101</z:seatnumber>
      </z:seats>
    </d:prop>
    <d:prop>
      <d:name>Smith</d:name>
    </d:prop>
  </d:set>
</d:propertyupdate>
In-depth page →
425Too EarlyUnderstand 425 Too Early: TLS early data replay risks, the Early-Data header, and server-side protection strategies.Example
→ REQUEST
GET /tech-news HTTP/1.1
Host: example.com
Early-Data: 1
In-depth page →
426Upgrade RequiredFix 426 Upgrade Required errors. Learn protocol upgrade requirements, the Upgrade header, and resolution steps.Example
→ REQUEST
GET /tech-news HTTP/1.1
Host: example.com
In-depth page →
428Precondition RequiredFix 428 Precondition Required errors. Learn conditional headers like If-Match and how to prevent lost updates.Example
→ REQUEST
PUT /reservations.txt HTTP/1.1
Host: example.com
In-depth page →
429Too Many RequestsToo many requests; rate limited.Example
→ REQUEST
GET /api/search HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 429 Too Many Requests
Retry-After: 30
Content-Type: application/json

{ "error": "rate limit exceeded" }
In-depth page →
431Request Header Fields Too LargeFix 431 Request Header Fields Too Large errors. Learn header size limits, cookie reduction, and troubleshooting steps.Example
→ REQUEST
GET /tech-news HTTP/1.1
Host: example.com
Cookie: first_cookie=<very_long>; second_cookie=<long_again>
In-depth page →
451Unavailable For Legal ReasonsUnderstand 451 Unavailable For Legal Reasons: censorship responses, legal demands, and Exchange ActiveSync usage.Example
→ REQUEST
GET /tech-trial-updates HTTP/1.1
Host: example.com
In-depth page →

5xxServer Error

500Internal Server ErrorAn internal server error occurred.Example
→ REQUEST
GET /report HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 500 Internal Server Error
Content-Type: application/json

{ "error": "unexpected server error" }
In-depth page →
501Not ImplementedFix 501 Not Implemented errors. Understand unsupported HTTP methods, differences from 405, and server configuration.Example
→ REQUEST
POST /requests?id=111&flag=start HTTP/1.1
Host: example.com
In-depth page →
502Bad GatewayThe gateway received an invalid response from upstream.Example
→ REQUEST
GET /api/users HTTP/1.1
Host: gateway.example.com
← RESPONSE
HTTP/1.1 502 Bad Gateway
Content-Type: text/plain

upstream sent an invalid response
In-depth page →
503Service UnavailableThe service is temporarily unavailable (overloaded or under maintenance).Example
→ REQUEST
GET / HTTP/1.1
Host: example.com
← RESPONSE
HTTP/1.1 503 Service Unavailable
Retry-After: 120
Content-Type: text/plain

under maintenance — try again shortly
In-depth page →
504Gateway TimeoutFix 504 Gateway Timeout errors. Learn upstream timeout causes, proxy configuration, and troubleshooting.Example
→ REQUEST
GET /news HTTP/1.1
Host: example.com
In-depth page →
505HTTP Version Not SupportedFix 505 HTTP Version Not Supported errors. Learn protocol version mismatches and server compatibility.Example
→ REQUEST
GET / HTTP/2
Host: example.com
In-depth page →
506Variant Also NegotiatesUnderstand 506 Variant Also Negotiates: transparent content negotiation circular references and server misconfiguration.Example
→ REQUEST
GET /docs HTTP/1.1
Host: example.com
Accept: text/html, application/xhtml+xml
In-depth page →
507Insufficient StorageFix 507 Insufficient Storage errors. Understand WebDAV storage limits, differences from 413, and resolution.Example
→ REQUEST
PUT /docs HTTP/1.1
Host: example.com
Content-Type: application/pdf
Content-Length: 10000

<PDF file included in message body>
In-depth page →
508Loop DetectedFix 508 Loop Detected errors. Understand WebDAV infinite loops and cPanel resource limit troubleshooting.Example
→ REQUEST
PROPFIND /shared/ HTTP/1.1
Host: example.com
Depth: infinity
Content-Type: application/xml
In-depth page →
510Not ExtendedUnderstand 510 Not Extended: the obsolete HTTP Extension Framework, its historic status, and usage.Example
→ REQUEST
GET /resource HTTP/1.1
Host: example.com
In-depth page →
511Network Authentication RequiredFix 511 Network Authentication Required errors. Understand captive portals, Wi-Fi login pages, and client handling.Example
→ REQUEST
GET / HTTP/1.1
Host: example.com
In-depth page →