Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| docker_notes:nginx-php-notes [2024-08-24 Sat wk34 10:42] – [Complete List] baumkp | docker_notes:nginx-php-notes [2024-08-24 Sat wk34 12:03] (current) – [Complete List] baumkp | ||
|---|---|---|---|
| Line 3138: | Line 3138: | ||
| =====HTTP Status Codes===== | =====HTTP Status Codes===== | ||
| ====Categories==== | ====Categories==== | ||
| - | ^Code ^Description^ | + | ^Code ^Name ^Description^ |
| - | |1XX |Informational | + | |1XX |Informational |
| - | |2XX |Successful | + | |2XX |Successful |
| - | |3XX |Redirects| | + | |3XX |Redirection |Further action needs to be taken in order to complete the request| |
| - | |4XX |Client Errors| | + | |4XX |Client Errors |
| - | |5XX |Server Errors| | + | |5XX |Server Errors |
| ====Complete List==== | ====Complete List==== | ||
| Line 3149: | Line 3149: | ||
| |100 |Continue |Everything so far is OK and that the client should continue with the request or ignore it if it is already finished.| | |100 |Continue |Everything so far is OK and that the client should continue with the request or ignore it if it is already finished.| | ||
| |101 |Switching Protocols |The client has asked the server to change protocols and the server has agreed to do so.| | |101 |Switching Protocols |The client has asked the server to change protocols and the server has agreed to do so.| | ||
| - | |102 |Processing |The server has received and is processing the request, but that it does not have a final response yet.| | + | |102 |Processing |The server has received and is processing the request, but that it does not have a final response yet. (depreciated, |
| - | |103 |Early Hints |Used to return some response headers before final HTTP message.| | + | |103 |Early Hints |Used to return some response headers before final HTTP message. |
| |200 |OK |Successful request.| | |200 |OK |Successful request.| | ||
| |201 |Created |The server acknowledged the created resource.| | |201 |Created |The server acknowledged the created resource.| | ||
| Line 3158: | Line 3158: | ||
| |205 |Reset Content |Tells the user agent to reset the document which sent this request.| | |205 |Reset Content |Tells the user agent to reset the document which sent this request.| | ||
| |206 |Partial Content |This response code is used when the range-header is sent from the client to request only part of a resource.| | |206 |Partial Content |This response code is used when the range-header is sent from the client to request only part of a resource.| | ||
| - | |207 |Multi-Status |Conveys information about multiple resources, for situations where multiple status codes might be appropriate.| | + | |207 |Multi-Status |Conveys information about multiple resources, for situations where multiple status codes might be appropriate. |
| - | |208 |Already Reported |The members of a DAV binding have already been enumerated in a preceding part of the multi-status response.| | + | |208 |Already Reported |The members of a DAV binding have already been enumerated in a preceding part of the multi-status response. |
| - | |226 |IM Used |IM is a specific extension of the HTTP protocol. The extension allows a HTTP server to send diffs (changes) of resources to clients.| | + | |218 |This is fine |A catch-all error condition allowing the passage of message bodies through the server when the ProxyErrorOverride setting is enabled. It is displayed in this situation instead of a 4xx or 5xx error message.< |
| + | |226 |IM Used |IM is a specific extension of the HTTP protocol. The extension allows a HTTP server to send diffs (changes) of resources to clients. | ||
| |300 |Multiple Choices |The request has more than one possible response. The user agent should choose one.| | |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. The new URL is given in the response.| | + | |301 |Moved Permanently |The URL of the requested resource has been changed permanently. |
| - | |302 |Found |This response code means that the URI of requested resource has been changed temporarily.| | + | |302 |Found |This response code means that the URI of 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.| | + | |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 |It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.| | |304 |Not Modified |It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.| | ||
| - | |305 |Use Proxy |Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. (discontinued)| | + | |305 |Use Proxy |Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. (discontinued, not used for security reasons)| |
| + | |306 |Switch Proxy |No longer used. Originally meant " | ||
| |307 |Temporary Redirect |The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request.| | |307 |Temporary Redirect |The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request.| | ||
| |308 |Permanent Redirect |This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header.| | |308 |Permanent Redirect |This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header.| | ||
| |400 |Bad Request |The server could not understand the request.| | |400 |Bad Request |The server could not understand the request.| | ||
| |401 |Unauthorized |The client didn't authenticate himself.| | |401 |Unauthorized |The client didn't authenticate himself.| | ||
| - | |402 |Payment Required |This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.| | + | |402 |Payment Required |The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists. |
| - | |403 |Forbidden |The client does not have access rights to the content.| | + | |403 |Forbidden |The client does not have access rights to the content. The request should not be repeated.| |
| - | |404 |Not Found |The server can not find the requested resource.| | + | |404 |Not Found |The server can not find the requested resource. Subsequent requests by the client are permissible.| |
| |405 |Method Not Allowed |The request method is known by the server but is not supported by the target 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 response doesn' | |406 |Not Acceptable |The response doesn' | ||
| Line 3187: | Line 3189: | ||
| |416 |Requested Range Not Satisfiable |The range specified by the Range header field in the request cannot be fulfilled.| | |416 |Requested Range Not Satisfiable |The range specified by the Range header field in the request cannot be fulfilled.| | ||
| |417 |Expectation Failed |The expectation indicated by the Expect request header field cannot be met by the server.| | |417 |Expectation Failed |The expectation indicated by the Expect request header field cannot be met by the server.| | ||
| - | |418 |I'm a teapot |The server refuses the attempt to brew coffee with a teapot.| | + | |418 |I'm a teapot |The server refuses the attempt to brew coffee with a teapot. |
| |421 |Misdirected Request |The request was directed at a server that is not able to produce a response.| | |421 |Misdirected Request |The request was directed at a server that is not able to produce a response.| | ||
| |422 |Unprocessable Entity |The request was well-formed but was unable to be followed due to semantic errors.| | |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.| | + | |423 |Locked |The resource that is being accessed is locked. |
| - | |424 |Failed Dependency |The request failed due to failure of a previous request.| | + | |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. (RFC 8470)| | ||
| |426 |Upgrade Required |The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.| | |426 |Upgrade Required |The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.| | ||
| - | |428 |Precondition Required |This response is intended to prevent the 'lost update' | + | |428 |Precondition Required |This response is intended to prevent the 'lost update' |
| - | |429 |Too Many Requests |The user has sent too many requests in a given amount of time.| | + | |429 |Too Many Requests |The user has sent too many requests in a given amount of time. (RFC 6585)| |
| - | |431 |Request Header Fields Too Large |The server is can't process the request because its header fields are too large.| | + | |431 |Request Header Fields Too Large |The server is can't process the request because its header fields are too large. |
| |444 |Connection Closed Without Response |The connection opened, but no data was written.| | |444 |Connection Closed Without Response |The connection opened, but no data was written.| | ||
| - | |451 |Unavailable For Legal Reasons |The user agent requested a resource that cannot legally be provided. (Such as, a web page censored by a government.)| | + | |451 |Unavailable For Legal Reasons |The user agent requested a resource that cannot legally be provided. (Such as, a web page <fc #ff0000>censored</ |
| |499 |Client Closed Request |The client closed the connection, despite the server was processing the request already.| | |499 |Client Closed Request |The client closed the connection, despite the server was processing the request already.| | ||
| |500 |Internal Server Error |The server has encountered a situation it does not know how to handle.| | |500 |Internal Server Error |The server has encountered a situation it does not know how to handle.| | ||
| Line 3205: | Line 3208: | ||
| |504 |Gateway Timeout |This error response is given when the server is acting as a gateway and cannot get a response in time.| | |504 |Gateway Timeout |This error response is given when 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.| | |505 |HTTP Version Not Supported |The HTTP version used in the request is not supported by the server.| | ||
| - | |506 |Variant Also Negotiates |The chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.| | + | |506 |Variant Also Negotiates |The chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process. |
| - | |507 |Insufficient Storage |The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.| | + | |507 |Insufficient Storage |The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. |
| - | |508 |Loop Detected |The server detected an infinite loop while processing 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.| | + | |509 |Bandwidth Limit Exceeded |The server has exceeded the bandwidth specified by the server administrator; |
| - | |511 |Network Authentication Required |Indicates that the client needs to authenticate to gain network access.| | + | |510 |Not Extended |Further extensions to the request are required for the server to fulfill it. (RFC 2774)| |
| - | |599 |Network Connect Timeout Error |The connection timed out due to a overloaded server, a hardware error or a infrastructure error.| | + | |511 |Network Authentication Required |Indicates that the client needs to authenticate to gain network access. |
| + | |598 |Network Read Timeout Error |Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy. (Informal convention)| | ||
| + | |599 |Network Connect Timeout Error |The connection timed out due to a overloaded server, a hardware error or a infrastructure error. | ||