Mirrors/httpstatuses
1
0
Fork 0
mirror of https://github.com/rmaake1/httpstatuses.git synced 2024-10-06 08:07:21 +02:00
Code Issues Packages Projects Releases Wiki Activity

Gives 5xx simple opening paragraphs

Browse Source
This commit is contained in:
Samuel Ryan 2015-11-07 05:48:31 +00:00
parent 0bc4c7f008
commit fee183c7f3
9 changed files with 29 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contents/codes/500.md
View File

@ -6,7 +6,7 @@ references:
"Rails HTTP Status Symbol": ":internal_server_error" "Rails HTTP Status Symbol": ":internal_server_error"
--- ---
The 500 (Internal Server Error) status code indicates that the server The 500 Internal Server Error status code indicates that the server
encountered an unexpected condition that prevented it from fulfilling the encountered an unexpected condition that prevented it from fulfilling the
request. request.

9
contents/codes/501.md
View File

@ -6,10 +6,11 @@ references:
"Rails HTTP Status Symbol": ":not_implemented" "Rails HTTP Status Symbol": ":not_implemented"
--- ---
The 501 (Not Implemented) status code indicates that the server does not support The 501 Not Implemented status code indicates that the server does not support
the functionality required to fulfill the request. This is the appropriate the functionality required to fulfill the request.
response when the server does not recognize the request method and is not
capable of supporting it for any resource. This is the appropriate response when the server does not recognize the request
method and is not capable of supporting it for any resource.
A 501 response is cacheable by default; i.e., unless otherwise indicated by the A 501 response is cacheable by default; i.e., unless otherwise indicated by the
method definition or explicit cache controls method definition or explicit cache controls

2
contents/codes/502.md
View File

@ -6,7 +6,7 @@ references:
"Rails HTTP Status Symbol": ":bad_gateway" "Rails HTTP Status Symbol": ":bad_gateway"
--- ---
The 502 (Bad Gateway) status code indicates that the server, while acting as a The 502 Bad Gateway status code indicates that the server, while acting as a
gateway or proxy, received an invalid response from an inbound server it gateway or proxy, received an invalid response from an inbound server it
accessed while attempting to fulfill the request. accessed while attempting to fulfill the request.

10
contents/codes/503.md
View File

@ -6,11 +6,13 @@ references:
"Rails HTTP Status Symbol": ":service_unavailable" "Rails HTTP Status Symbol": ":service_unavailable"
--- ---
The 503 (Service Unavailable) status code indicates that the server is currently The 503 Service Unavailable status code indicates that the server is currently
unable to handle the request due to a temporary overload or scheduled unable to handle the request due to a temporary overload or scheduled
maintenance, which will likely be alleviated after some delay. The server MAY maintenance, which will likely be alleviated after some delay.
send a Retry-After header field ([RFC7231 Section 7.1.3][2]) to suggest an
appropriate amount of time for the client to wait before retrying the request. The server MAY send a Retry-After header field ([RFC7231 Section 7.1.3][2]) to
suggest an appropriate amount of time for the client to wait before retrying the
request.
Note: The existence of the 503 status code does not imply that a server has to Note: The existence of the 503 status code does not imply that a server has to
use it when becoming overloaded. Some servers might simply refuse the use it when becoming overloaded. Some servers might simply refuse the

2
contents/codes/504.md
View File

@ -6,7 +6,7 @@ references:
"Rails HTTP Status Symbol": ":gateway_timeout" "Rails HTTP Status Symbol": ":gateway_timeout"
--- ---
The 504 (Gateway Timeout) status code indicates that the server, while acting as The 504 Gateway Timeout status code indicates that the server, while acting as
a gateway or proxy, did not receive a timely response from an upstream server it a gateway or proxy, did not receive a timely response from an upstream server it
needed to access in order to complete the request. needed to access in order to complete the request.

8
contents/codes/505.md
View File

@ -6,10 +6,12 @@ references:
"Rails HTTP Status Symbol": ":http_version_not_supported" "Rails HTTP Status Symbol": ":http_version_not_supported"
--- ---
The 505 (HTTP Version Not Supported) status code indicates that the server does The 505 HTTP Version Not Supported status code indicates that the server does
not support, or refuses to support, the major version of HTTP that was used in not support, or refuses to support, the major version of HTTP that was used in
the request message. The server is indicating that it is unable or unwilling to the request message.
complete the request using the same major version as the client, as described in
The server is indicating that it is unable or unwilling to complete the request
using the same major version as the client, as described in
[Section 2.6 of RFC7230][2], other than with this error message. The server [Section 2.6 of RFC7230][2], other than with this error message. The server
SHOULD generate a representation for the 505 response that describes why that SHOULD generate a representation for the 505 response that describes why that
version is not supported and what other protocols are supported by that server. version is not supported and what other protocols are supported by that server.

11
contents/codes/507.md
View File

@ -6,11 +6,12 @@ references:
"Rails HTTP Status Symbol": ":insufficient_storage" "Rails HTTP Status Symbol": ":insufficient_storage"
--- ---
The 507 (Insufficient Storage) status code means the method could not be The 507 Insufficient Storage status code means the method could not be
performed on the resource because the server is unable to store the performed on the resource because the server is unable to store the
representation needed to successfully complete the request. This condition is representation needed to successfully complete the request.
considered to be temporary. If the request that received this status code was
the result of a user action, the request MUST NOT be repeated until it is This condition is considered to be temporary. If the request that received this
requested by a separate user action. status code was the result of a user action, the request MUST NOT be repeated
until it is requested by a separate user action.
[1]: <http://tools.ietf.org/html/rfc4918#section-11.5> [1]: <http://tools.ietf.org/html/rfc4918#section-11.5>

2
contents/codes/508.md
View File

@ -4,7 +4,7 @@ code: 508
title: Loop Detected title: Loop Detected
--- ---
The 508 (Loop Detected) status code indicates that the server terminated an The 508 Loop Detected status code indicates that the server terminated an
operation because it encountered an infinite loop while processing a request operation because it encountered an infinite loop while processing a request
with "Depth: infinity". This status indicates that the entire operation failed. with "Depth: infinity". This status indicates that the entire operation failed.

4
contents/codes/510.md
View File

@ -8,7 +8,9 @@ references:
The policy for accessing the resource has not been met in the request. The The policy for accessing the resource has not been met in the request. The
server should send back all the information necessary for the client to issue an server should send back all the information necessary for the client to issue an
extended request. It is outside the scope of this specification to specify how extended request.
It is outside the scope of this specification to specify how
the extensions inform the client. the extensions inform the client.
If the 510 response contains information about extensions that were not present If the 510 response contains information about extensions that were not present