Baserad på https://datatracker.ietf.org/doc/html/rfc7231#section-6
HTTP-status | Beskrivning | Hantering |
---|---|---|
| The 1xx (Informational) class of status code indicates an interim response for communicating connection status or request progress prior to completing the requested action and sending a final response. | Ingen hantering krävs. Ramverken brukar sköta automatiskt. |
| The 2xx (Successful) class of status code indicates that the client's request was successfully received, understood, and accepted. | Ingen hantering krävs. Anropet gick bra. |
| The 300 (Multiple Choices) status code indicates that the target resource has more than one representation, each with its own more specific identifier, and information about the alternatives is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to one or more of those identifiers. In other words, the server desires that the user agent engage in reactive negotiation to select the most appropriate representation(s) for its needs (). | Används inte hos oss. |
| The 301 (Moved Permanently) status code indicates that the target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs. Clients with link-editing capabilities ought to automatically re-link references to the effective request URI to one or more of the new references sent by the server, where possible. | Navigera till ny URI. Denna URI ska följa med i en Location-header i responsen. |
| The 302 (Found) status code indicates that the target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client ought to continue to use the effective request URI for future requests. | Navigera till ny URI. Denna URI ska följa med i en Location-header i responsen. Byt URI som används i anropet. |
| The 303 (See Other) status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request. A user agent can perform a retrieval request targeting that URI (a GET or HEAD request if using HTTP), which might also be redirected, and present the eventual result as an answer to the original request. Note that the new URI in the Location header field is not considered equivalent to the effective request URI. | Hämta resursen på URI som följer med i Location-header i responsen. |
| The 305 (Use Proxy) status code was defined in a previous version of this specification and is now deprecated (Appendix B). | Deprecated och används inte hos oss. |
| The 306 status code was defined in a previous version of this specification, is no longer used, and the code is reserved. | Används inte hos oss. |
| The 307 (Temporary Redirect) status code indicates that the target resource resides temporarily under a different URI and the user agent MUST NOT change the request method if it performs an automatic redirection to that URI. Since the redirection can change over time, the client ought to continue using the original effective request URI for future requests. | Samma som 302 med skillnaden att URI som används i anropet inte ska ändras. |
| The 400 (Bad Request) status code indicates that 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). | Inga omförsök ska göras. Det är något fel på anropet och det behöver korrigeras innan det är lönt att göra ett nytt anrop. |
|
| Används inte hos oss. |