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 11:51] – [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 3160: | Line 3160: | ||
| |207 |Multi-Status |Conveys information about multiple resources, for situations where multiple status codes might be appropriate. (WebDAV related, RFC 4918| | |207 |Multi-Status |Conveys information about multiple resources, for situations where multiple status codes might be appropriate. (WebDAV related, RFC 4918| | ||
| |208 |Already Reported |The members of a DAV binding have already been enumerated in a preceding part of the multi-status response. (WebDAV related, RFC 3229| | |208 |Already Reported |The members of a DAV binding have already been enumerated in a preceding part of the multi-status response. (WebDAV related, RFC 3229| | ||
| - | |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. (Apache HTTP Server). | | + | |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.<fc # |
| |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. (RFC 3229)| | |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. (RFC 3229)| | ||
| |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, | ||
| Line 3173: | Line 3173: | ||
| |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 3189: | 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. (RFC 2323, RFC 7168) An April Fool's joke.| | + | |418 |I'm a teapot |The server refuses the attempt to brew coffee with a teapot. (RFC 2323, RFC 7168) <fc #ff0000>An April Fool's joke.</fc>| |
| |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.| | ||
| Line 3200: | Line 3200: | ||
| |431 |Request Header Fields Too Large |The server is can't process the request because its header fields are too large. (RFC 6585)| | |431 |Request Header Fields Too Large |The server is can't process the request because its header fields are too large. (RFC 6585)| | ||
| |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 was chosen as famous reference to the future fantasy book, Fahrenheit 451 dealing with government censorship. | + | |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.| | ||