HTTP-Statuscodes

Durchsuchen Sie HTTP-Statuscodes mit Beschreibungen und Kategorien

Suche

Kategorie

Code	Name	Beschreibung
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 the final HTTP message.
200	OK	The request has succeeded. The meaning of the success depends on the HTTP method.
201	Created	The request has been fulfilled and has resulted in one or more new resources being created.
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 the origin server.
204	No Content	The server has fulfilled the request but does not need to return a response body.
205	Reset Content	The server has fulfilled the request and the user agent should reset the document view.
206	Partial Content	The server is delivering only part of the resource due to a range header sent by the client.
300	Multiple Choices	The request has more than one possible response. The user agent should choose one.
301	Moved Permanently	The URL of the requested resource has been changed permanently.
302	Found	The URL of the requested resource has been changed temporarily.
303	See Other	The server sent this response to direct the client to get the requested resource at another URI with a GET request.
304	Not Modified	The resource has not been modified since the version specified by the request headers.
305	Use Proxy	The requested resource must be accessed through the proxy given by the Location field.
307	Temporary Redirect	The server sends this response to direct the client to get the requested resource at another URI with the same method.
308	Permanent Redirect	The resource has been moved permanently to the URL given by the Location headers.
400	Bad Request	The server cannot or will not process the request due to something that is perceived to be a client error.
401	Unauthorized	The client must authenticate itself to get the requested response.
402	Payment Required	This response code is reserved for future use. The initial aim was for digital payment systems.
403	Forbidden	The client does not have access rights to the content.
404	Not Found	The server cannot find the requested resource.
405	Method Not Allowed	The request method is known by the server but is not supported by the target resource.
406	Not Acceptable	The server cannot produce a response matching the list of acceptable values defined in the request headers.
407	Proxy Authentication Required	The client must first authenticate itself with the proxy.
408	Request Timeout	The server would like to shut down this unused connection.
409	Conflict	The request conflicts with the current state of the server.
410	Gone	The requested content has been permanently deleted from the server.
411	Length Required	The server refuses to accept the request without a defined Content-Length header.
412	Precondition Failed	The client has indicated preconditions in its headers which the server does not meet.
413	Payload Too Large	The request entity is larger than limits defined by the server.
414	URI Too Long	The URI requested by the client is longer than the server is willing to interpret.
415	Unsupported Media Type	The media format of the requested data is not supported by the server.
416	Range Not Satisfiable	The range specified by the Range header cannot be fulfilled.
417	Expectation Failed	The expectation indicated by the Expect request header cannot be met by the server.
418	I'm a Teapot	The server refuses the attempt to brew coffee with a teapot.
422	Unprocessable Entity	The request was well-formed but was unable to be followed due to semantic errors.
423	Locked	The resource that is being accessed is locked.
424	Failed Dependency	The request failed due to failure of a previous request.
425	Too Early	Indicates that the server is unwilling to risk processing a request that might be replayed.
426	Upgrade Required	The server refuses to perform the request using the current protocol.
429	Too Many Requests	The user has sent too many requests in a given amount of time.
431	Request Header Fields Too Large	The server is unwilling to process the request because its header fields are too large.
451	Unavailable For Legal Reasons	The requested resource is unavailable due to legal demands.
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 the upstream server.
503	Service Unavailable	The server is not ready to handle the request.
504	Gateway Timeout	The server is acting as a gateway and cannot get a response in time.
505	HTTP Version Not Supported	The HTTP version used in the request is not supported by the server.
506	Variant Also Negotiates	The server has an internal configuration error.
507	Insufficient Storage	The server is unable to store the representation needed to complete the request.
508	Loop Detected	The server detected an infinite loop while processing the request.
510	Not Extended	Further extensions to the request are required for the server to fulfill it.
511	Network Authentication Required	The client needs to authenticate to gain network access.

57 Code

Verwendung

Durchsuchen Sie die vollständige Liste der HTTP-Statuscodes. Verwenden Sie das Suchfeld, um Codes nach Nummer oder Namen zu finden, oder filtern Sie mit dem Dropdown-Menü nach Kategorie.

HTTP-Statuscodes

Verwendung

Verwandte Tools

Diese Seite teilen

Scannen, um auf WeChat zu teilen