HTTP Statuskoder - Gratis Online | ToolXHub
Bruk HTTP Statuskoder gratis online, ingen nedlasting nødvendig. ToolXHub tilbyr hundrevis av morsomme onlineverktøy.
1xx
Informational 信息响应
4 koder 100
Continue
The server has received the request headers and the client should proceed to send the request body.
The initial part of a request has been received and the client should continue with the request or ignore the response if the request is already finished.
101
Switching Protocols
The server agrees to switch protocols as requested by the client via the Upgrade header.
Sent in response to an Upgrade request header from the client. The server indicates which protocol it is switching to.
102
Processing
The server has received and is processing the request, but no response is available yet (WebDAV).
Used to prevent the client from timing out while a long-running request is being processed. Primarily used in WebDAV.
103
Early Hints
Used to return some response headers before the final HTTP message, allowing preloading.
Typically used with the Link header to allow the user agent to start preloading resources while the server prepares a response.
2xx
Success 成功
7 koder 200
OK
The request has succeeded. The meaning depends on the HTTP method used.
GET: The resource has been fetched and is transmitted in the message body. HEAD: The representation headers are included without any message body. POST: The resource describing the result of the action is transmitted in the message body.
201
Created
The request has succeeded and a new resource has been created as a result.
Typically the response to a POST or some PUT requests. The new resource, or a description and link to it, is returned in the response body.
202
Accepted
The request has been accepted for processing, but the processing has not been completed.
Used for asynchronous processing. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.
203
Non-Authoritative Information
The returned metadata is not exactly the same as available from the origin server.
This response code means the returned metadata is not exactly the same as is available from the origin server, but is collected from a local or third-party copy.
204
No Content
The server successfully processed the request, but is not returning any content.
The server has successfully fulfilled the request and there is no additional content to send in the response payload body. The user agent may update its cached headers.
205
Reset Content
The server successfully processed the request and asks the client to reset the document view.
Tells the user agent to reset the document which sent this request. Useful for clearing form data after a successful submission.
206
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
Used when the client sends a Range header to request only part of a resource. The response includes a Content-Range header indicating the byte range.
3xx
Redirection 重定向
7 koder 300
Multiple Choices
The request has more than one possible response. The user agent should choose one.
There are multiple options for the resource from which the client may choose. The response includes a list of links from which the user or user agent can select.
301
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
Search engines update their links to the resource. Browsers automatically redirect to the new URL. Use this for permanent URL changes.
302
Found
The resource is temporarily located at a different URI. The client should continue to use the original URI.
Historically known as "Moved Temporarily". The redirect may be changed on occasion, so the client should continue to use the original URI for future requests.
303
See Other
The server sends this response to direct the client to get the requested resource at another URI with a GET request.
Used after a POST/PUT/DELETE to redirect the client to a different resource. The client must use GET to retrieve the new resource.
304
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
Used for caching purposes. The response has no body, and tells the client that its cached version is still good to use.
307
Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI with the same method.
Unlike 302, the method and body of the original request must not be changed when the redirected request is made. The resource is temporarily at another URI.
308
Permanent Redirect
The resource is now permanently located at another URI, and the same method must be used.
Like 301, but the method and body of the original request must not be changed when the redirected request is made. Use for permanent method-preserving redirects.
4xx
Client Errors 客户端错误
18 koder 400
Bad Request
The server cannot process the request due to a client error, such as malformed request syntax.
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
401
Unauthorized
The client must authenticate itself to get the requested response.
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". The client must authenticate itself to get the requested response.
402
Payment Required
Reserved for future use. Originally intended for digital payment systems.
This code is reserved for future use. It was originally created to be used as part of a digital cash or micropayment system, but that has not happened yet.
403
Forbidden
The client does not have access rights to the content. Unlike 401, re-authenticating makes no difference.
The server understood the request but refuses to authorize it. Unlike 401, the client's identity is known but they do not have the necessary permissions.
404
Not Found
The server cannot find the requested resource. This is the most famous HTTP status code.
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The most recognizable HTTP status code.
405
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
The method specified in the request is not allowed for the resource identified by the Request-URI. The response must include an Allow header containing a list of valid methods.
406
Not Acceptable
The server cannot produce a response matching the list of acceptable values defined in the request headers.
Sent when the server cannot produce a response matching the list of acceptable values defined in the proactive content negotiation headers, such as Accept, Accept-Language, Accept-Encoding.
408
Request Timeout
The server timed out waiting for the request from the client.
The server would like to shut down this unused connection. Sent on an idle connection by some servers, even without any previous request by the client.
409
Conflict
The request could not be completed due to a conflict with the current state of the resource.
This code is used in situations where the user might be able to resolve the conflict and resubmit the request. Typically occurs with PUT requests when there is a version conflict.
410
Gone
The requested content has been permanently deleted from the server, with no forwarding address.
This response is similar to 404, but used when the resource was previously available but is now intentionally removed and will not be available again. Clients should purge their cached links.
411
Length Required
The server refuses to accept the request without a defined Content-Length header.
The server requires the request to include a Content-Length header. The client may repeat the request if it adds a valid Content-Length header.
413
Payload Too Large
The request entity is larger than limits defined by the server. The server might close the connection.
The server is refusing to process a request because the request payload is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing.
414
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
This occurs when the client has improperly converted a POST to a GET with long query information, or when the client is attempting to exploit security vulnerabilities.
415
Unsupported Media Type
The server refuses to accept the request because the payload format is in an unsupported format.
The media format of the requested data is not supported by the server. For example, the client uploads an image as image/webp, but the server only accepts image/jpeg.
418 ★
I'm a teapot
The server refuses to brew coffee because it is, permanently, a teapot. An April Fools' joke from 1998.
This code was defined in 1998 as an April Fools' joke in RFC 2324, Hyper Text Coffee Pot Control Protocol. It is not expected to be implemented by actual HTTP servers, but many have done so as an easter egg.
422
Unprocessable Entity
The server understands the content type but was unable to process the contained instructions.
The request was well-formed but was unable to be followed due to semantic errors. Commonly used in WebDAV and REST APIs for validation errors (e.g., Rails, Laravel).
429
Too Many Requests
The user has sent too many requests in a given amount of time ("rate limiting").
The user has sent too many requests in a given time period. The response should include a Retry-After header indicating how long to wait before making a new request.
451 ★
Unavailable For Legal Reasons
The server is denying access to the resource as a consequence of a legal demand.
A reference to the novel Fahrenheit 451 (the temperature at which paper burns). Used when access to a resource is restricted due to legal demands, such as censorship or government-mandated blocks.
5xx
Server Errors 服务器错误
6 koder 500
Internal Server Error
The server has encountered a situation it does not know how to handle.
A generic error message indicating the server encountered an unexpected condition that prevented it from fulfilling the request. This is the most common server-side error.
501
Not Implemented
The request method is not supported by the server and cannot be handled.
The server does not recognize the request method or lacks the ability to fulfill the request. This implies the method might be available in the future.
502
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
Occurs when a server acting as a gateway or proxy receives an invalid response from an inbound server. Common in Nginx setups when the upstream server is down or misconfigured.
503
Service Unavailable
The server is not ready to handle the request. Common causes include server maintenance or overload.
The server is currently unable to handle the request due to temporary overloading or maintenance. The response should include a Retry-After header indicating when the service is expected to be available.
504
Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.
Similar to 502 but specifically indicates a timeout. The upstream server took too long to respond, and the gateway gave up waiting.
505
HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
The server does not support, or refuses to support, the major version of HTTP that was used in the request message. The response should describe why and which versions are supported.
Om dette verktøyet
HTTP Statuskoder er et gratis online utviklerverktøy. HTTP statuskode oppslagstavle, med klassifisering og detaljert beskrivelse. Perfekt for å fokusere, slappe av eller bare ha det gøy. Det kjører helt i nettleseren din — ingen nedlasting eller registrering.
Skriv inn statuskode (som 404) eller nøkkelord (som not found), og verktøyet vil vise full informasjon om denne statuskoden: offisiell definisjon, forklaring på betydning, vanlige årsaker, løsninger og relaterte statuskoder. Støtter gjennomgang etter kategori: 1xx Informasjon, 2xx Suksess, 3xx Omdirigering, 4xx Klientfeil, 5xx Serverfeil.
Egnet for utviklere som raskt ønsker å forstå betydningen av statuskoder når de feilsøker API, eller for å spore feil ved nettlesertilgang. Mer presist enn søkemotorer, viser direkte autoritative forklaringer.
Dataene kommer fra IETF RFC-dokumenter og MDN Web Docs, og inkluderer alle standardstatuskoder og noen ikke-standard, men ofte brukte statuskoder (som 419 Page Expired). Hver statuskode har en detaljert forklaring på kinesisk og faktiske bruksscenarier.
HTTP statusskode søkeverktøy, raskt finn betydningen, bruksscenarier og relaterte dokumenter for HTTP statusskoder, støtter søk og kategoribasert gjennomgang.