data.toml

[100]
code = 100
phrase = "Continue"
class = "1XX Informational"
description = """
The 100 (Continue) status code indicates that the initial part of a \
request has been received and has not yet been rejected by the \
server. The server intends to send a final response after the \
request has been fully received and acted upon.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.2.1"

[101]
code = 101
phrase = "Switching Protocols"
class = "1XX Informational"
description = """
The 101 (Switching Protocols) status code indicates that the server \
understands and is willing to comply with the client's request, via \
the Upgrade header field, for a change in \
the application protocol being used on this connection. The server \
MUST generate an Upgrade header field in the response that indicates \
which protocol(s) will be switched to immediately after the empty \
line that terminates the 101 response.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.2.2"

[102]
code = 102
phrase = "Processing"
class = "1XX Informational"
description = """
The 102 (Processing) status code is an interim response used to \
inform the client that the server has accepted the complete request, \
but has not yet completed it. This status code SHOULD only be sent \
when the server has a reasonable expectation that the request will \
take significant time to complete. As guidance, if a method is taking \
longer than 20 seconds (a reasonable, but arbitrary value) to process \
the server SHOULD return a 102 (Processing) response. The server MUST \
send a final response after the request has been completed.\
"""
reference = "https://tools.ietf.org/html/rfc2518#section-10.1"


[103]
code = 103
phrase = "Early Hints"
class = "1XX Informational"
description = """
The 103 (Early Hints) informational status code indicates to the \
client that the server is likely to send a final response with the \
header fields included in the informational response.\
"""
reference = "https://tools.ietf.org/html/rfc8297#section-2"

[200]
code = 200
phrase = "OK"
class = "2XX Successful"
description = """
The 200 (OK) status code indicates that the request has succeeded. \
The payload sent in a 200 response depends on the request method. \
For the methods defined by this specification, the intended meaning \
of the payload can be summarized as:

* GET : a representation of the target resource;
* HEAD : the same representation as GET, but without the representation data;
* POST : a representation of the status of, or results obtained from, the action;
* PUT, DELETE : a representation of the status of the action;
* OPTIONS : a representation of the communications options;
* TRACE : a representation of the request message as received by the end server.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.3.1"

[201]
code = 201
phrase = "Created"
class = "2XX Successful"
description = """
The 201 (Created) status code indicates that the request has been \
fulfilled and has resulted in one or more new resources being \
created. The primary resource created by the request is identified \
by either a Location header field in the response or, if no Location \
field is received, by the effective request URI.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.3.2"

[202]
code = 202
phrase = "Accepted"
class = "2XX Successful"
description = """
The 202 (Accepted) status code indicates that the request has been \
accepted for processing, but the processing has not been completed. \
The request might or might not eventually be acted upon, as it might \
be disallowed when processing actually takes place. There is no \
facility in HTTP for re-sending a status code from an asynchronous \
operation.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.3.3"

[203]
code = 203
phrase = "Non-Authoritative Information"
class = "2XX Successful"
description = """
The 203 (Non-Authoritative Information) status code indicates that \
the request was successful but the enclosed payload has been modified \
from that of the origin server's 200 (OK) response by a transforming \
proxy. This status code allows the \
proxy to notify recipients when a transformation has been applied, \
since that knowledge might impact later decisions regarding the \
content. For example, future cache validation requests for the \
content might only be applicable along the same request path (through \
the same proxies).\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.3.4"

[204]
code = 204
phrase = "No Content"
class = "2XX Successful"
description = """
The 204 (No Content) status code indicates that the server has \
successfully fulfilled the request and that there is no additional \
content to send in the response payload body. Metadata in the \
response header fields refer to the target resource and its selected \
representation after the requested action was applied.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.3.5"

[205]
code = 205
phrase = "Reset Content"
class = "2XX Successful"
description = """
The 205 (Reset Content) status code indicates that the server has \
fulfilled the request and desires that the user agent reset the \
"document view", which caused the request to be sent, to its original \
state as received from the origin server.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.3.6"

[206]
code = 206
phrase = "Partial Content"
class = "2XX Successful"
description = """
The 206 (Partial Content) status code indicates that the server is \
successfully fulfilling a range request for the target resource by \
transferring one or more parts of the selected representation that \
correspond to the satisfiable ranges found in the request's Range \
header field.\
"""
reference = "https://tools.ietf.org/html/rfc7233#section-4.1"

[207]
code = 207
phrase = "Multi-Status"
class = "2XX Successful"
description = """
The 207 (Multi-Status) status code provides status for multiple \
independent operations.\
"""
reference = "https://tools.ietf.org/html/rfc4918#section-11.1"

[208]
code = 208
phrase = "Already Reported"
class = "2XX Successful"
description = """
The 208 (Already Reported) status code can be used inside a DAV: \
propstat response element to avoid enumerating the internal members \
of multiple bindings to the same collection repeatedly. For each \
binding to a collection inside the request's scope, only one will be \
reported with a 200 status, while subsequent DAV:response elements \
for all other bindings will use the 208 status, and no DAV:response \
elements for their descendants are included.\
"""
reference = "https://tools.ietf.org/html/rfc5842#section-7.1"

[226]
code = 226
phrase = "IM Used"
class = "2XX Successful"
description = """
The server has fulfilled a GET request for the resource, and the \
response is a representation of the result of one or more instance- \
manipulations applied to the current instance. The actual current \
instance might not be available except by combining this response \
with other previous or future responses, as appropriate for the \
specific instance-manipulation(s). If so, the headers of the \
resulting instance are the result of combining the headers from the \
status-226 response and the other instances, following the rules in \
section 13.5.3 of the HTTP/1.1 specification.\
"""
reference = "https://tools.ietf.org/html/rfc3229#section-10.4.1"

[300]
code = 300
phrase = "Multiple Choices"
class = "3XX Redirection"
description = """
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.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.4.1"

[301]
code = 301
phrase = "Moved Permanently"
class = "3XX Redirection"
description = """
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.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.4.2"

[302]
code = 302
phrase = "Found"
class = "3XX Redirection"
description = """
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.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.4.3"

[303]
code = 303
phrase = "See Other"
class = "3XX Redirection"
description = """
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.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.4.4"

[304]
code = 304
phrase = "Not Modified"
class = "3XX Redirection"
description = """
The 304 (Not Modified) status code indicates that a conditional GET \
or HEAD request has been received and would have resulted in a 200 \
(OK) response if it were not for the fact that the condition \
evaluated to false. In other words, there is no need for the server \
to transfer a representation of the target resource because the \
request indicates that the client, which made the request \
conditional, already has a valid representation; the server is \
therefore redirecting the client to make use of that stored \
representation as if it were the payload of a 200 (OK) response.\
"""
reference = "https://tools.ietf.org/html/rfc7232#section-4.1"

[305]
code = 305
phrase = "Use Proxy"
class = "3XX Redirection"
description = """
Deprecated.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.4.5"

[306]
code = 306
phrase = "Unused"
class = "3XX Redirection"
description = """
No longer used, reserved.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.4.6"

[307]
code = 307
phrase = "Temporary Redirect"
class = "3XX Redirection"
description = """
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.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.4.7"

[308]
code = 308
phrase = "Permanent Redirect"
class = "3XX Redirection"
description = """
The 308 (Permanent Redirect) 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.\
"""
reference = "https://tools.ietf.org/html/rfc7538#section-3"

[400]
code = 400
phrase = "Bad Request"
class = "4XX Client Error"
description = """
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).\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.1"

[401]
code = 401
phrase = "Unauthorized"
class = "4XX Client Error"
description = """
The 401 (Unauthorized) status code indicates that the request has not \
been applied because it lacks valid authentication credentials for \
the target resource. The server generating a 401 response MUST send \
a WWW-Authenticate header field containing at least one \
challenge applicable to the target resource.\
"""
reference = "https://tools.ietf.org/html/rfc7235#section-3.1"

[402]
code = 402
phrase = "Payment Required"
class = "4XX Client Error"
description = """
The 402 (Payment Required) status code is reserved for future use.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.2"

[403]
code = 403
phrase = "Forbidden"
class = "4XX Client Error"
description = """
The 403 (Forbidden) status code indicates that the server understood \
the request but refuses to authorize it. A server that wishes to \
make public why the request has been forbidden can describe that \
reason in the response payload (if any).\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.3"

[404]
code = 404
phrase = "Not Found"
class = "4XX Client Error"
description = """
The 404 (Not Found) status code indicates that the origin server did \
not find a current representation for the target resource or is not \
willing to disclose that one exists. A 404 status code does not \
indicate whether this lack of representation is temporary or \
permanent; the 410 (Gone) status code is preferred over 404 if the \
origin server knows, presumably through some configurable means, that \
the condition is likely to be permanent.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.4"

[405]
code = 405
phrase = "Method Not Allowed"
class = "4XX Client Error"
description = """
The 405 (Method Not Allowed) status code indicates that the method \
received in the request-line is known by the origin server but not \
supported by the target resource. The origin server MUST generate an \
Allow header field in a 405 response containing a list of the target \
resource's currently supported methods.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.5"

[406]
code = 406
phrase = "Not Acceptable"
class = "4XX Client Error"
description = """
The 406 (Not Acceptable) status code indicates that the target \
resource does not have a current representation that would be \
acceptable to the user agent, according to the proactive negotiation \
header fields received in the request, and the server \
is unwilling to supply a default representation.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.6"

[407]
code = 407
phrase = "Proxy Authentication Required"
class = "4XX Client Error"
description = """
The 407 (Proxy Authentication Required) status code is similar to 401 \
(Unauthorized), but it indicates that the client needs to \
authenticate itself in order to use a proxy. The proxy MUST send a \
Proxy-Authenticate header field containing a challenge \
applicable to that proxy for the target resource. The client MAY \
repeat the request with a new or replaced Proxy-Authorization header \
field.\
"""
reference = "https://tools.ietf.org/html/rfc7235#section-3.2"

[408]
code = 408
phrase = "Request Timeout"
class = "4XX Client Error"
description = """
The 408 (Request Timeout) status code indicates that the server did \
not receive a complete request message within the time that it was \
prepared to wait. A server SHOULD send the "close" connection option \
in the response, since 408 implies that \
the server has decided to close the connection rather than continue \
waiting. If the client has an outstanding request in transit, the \
client MAY repeat that request on a new connection.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.7"

[409]
code = 409
phrase = "Conflict"
class = "4XX Client Error"
description = """
The 409 (Conflict) status code indicates that the request could not \
be completed due to a conflict with the current state of the target \
resource. This code is used in situations where the user might be \
able to resolve the conflict and resubmit the request. The server \
SHOULD generate a payload that includes enough information for a user \
to recognize the source of the conflict.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.8"

[410]
code = 410
phrase = "Gone"
class = "4XX Client Error"
description = """
The 410 (Gone) status code indicates that access to the target \
resource is no longer available at the origin server and that this \
condition is likely to be permanent. If the origin server does not \
know, or has no facility to determine, whether or not the condition \
is permanent, the status code 404 (Not Found) ought to be used \
instead.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.9"

[411]
code = 411
phrase = "Length Required"
class = "4XX Client Error"
description = """
The 411 (Length Required) status code indicates that the server \
refuses to accept the request without a defined Content-Length. \
The client MAY repeat the request if \
it adds a valid Content-Length header field containing the length of \
the message body in the request message.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.10"

[412]
code = 412
phrase = "Precondition Failed"
class = "4XX Client Error"
description = """
The 412 (Precondition Failed) status code indicates that one or more \
conditions given in the request header fields evaluated to false when \
tested on the server. This response code allows the client to place \
preconditions on the current resource state (its current \
representations and metadata) and, thus, prevent the request method \
from being applied if the target resource is in an unexpected state.\
"""
reference = "https://tools.ietf.org/html/rfc7232#section-4.2"

[413]
code = 413
phrase = "Payload Too Large"
class = "4XX Client Error"
description = """
The 413 (Payload Too Large) status code indicates that the server is \
refusing to process a request because the request payload is larger \
than the server is willing or able to process. The server MAY close \
the connection to prevent the client from continuing the request.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.11"


[414]
code = 414
phrase = "URI Too Long"
class = "4XX Client Error"
description = """
The 414 (URI Too Long) status code indicates that the server is \
refusing to service the request because the request-target \
is longer than the server is willing to interpret. \
This rare condition is only likely to occur when a client has \
improperly converted a POST request to a GET request with long query \
information, when the client has descended into a "black hole" of \
redirection (e.g., a redirected URI prefix that points to a suffix of \
itself) or when the server is under attack by a client attempting to \
exploit potential security holes.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.12"

[415]
code = 415
phrase = "Unsupported Media Type"
class = "4XX Client Error"
description = """
The 415 (Unsupported Media Type) status code indicates that the \
origin server is refusing to service the request because the payload \
is in a format not supported by this method on the target resource. \
The format problem might be due to the request's indicated \
Content-Type or Content-Encoding, or as a result of inspecting the \
data directly.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.13"

[416]
code = 416
phrase = "Range Not Satisfiable"
class = "4XX Client Error"
description = """
The 416 (Range Not Satisfiable) status code indicates that none of \
the ranges in the request's Range header field overlap \
the current extent of the selected resource or that the set of ranges \
requested has been rejected due to invalid ranges or an excessive \
request of small or overlapping ranges.\
"""
reference = "https://tools.ietf.org/html/rfc7233#section-4.4"

[417]
code = 417
phrase = "Expectation Failed"
class = "4XX Client Error"
description = """
The 417 (Expectation Failed) status code indicates that the \
expectation given in the request's Expect header field \
could not be met by at least one of the inbound \
servers.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.14"

[421]
code = 421
phrase = "Misdirected Request"
class = "4XX Client Error"
description = """
The 421 (Misdirected Request) status code indicates that the request \
was directed at a server that is not able to produce a response. \
This can be sent by a server that is not configured to produce \
responses for the combination of scheme and authority that are \
included in the request URI.\
"""
reference = "https://tools.ietf.org/html/rfc7540#section-9.1.2"

[422]
code = 422
phrase = "Unprocessable Entity"
class = "4XX Client Error"
description = """
The 422 (Unprocessable Entity) status code means the server \
understands the content type of the request entity (hence a \
415(Unsupported Media Type) status code is inappropriate), and the \
syntax of the request entity is correct (thus a 400 (Bad Request) \
status code is inappropriate) but was unable to process the contained \
instructions. For example, this error condition may occur if an XML \
request body contains well-formed (i.e., syntactically correct), but \
semantically erroneous, XML instructions.\
"""
reference = "https://tools.ietf.org/html/rfc4918#section-11.2"

[423]
code = 423
phrase = "Locked"
class = "4XX Client Error"
description = """
The 423 (Locked) status code means the source or destination resource \
of a method is locked. This response SHOULD contain an appropriate \
precondition or postcondition code, such as 'lock-token-submitted' or \
'no-conflicting-lock'.\
"""
reference = "https://tools.ietf.org/html/rfc4918#section-11.3"

[424]
code = 424
phrase = "Failed Dependency"
class = "4XX Client Error"
description = """
The 424 (Failed Dependency) status code means that the method could \
not be performed on the resource because the requested action \
depended on another action and that action failed. For example, if a \
command in a PROPPATCH method fails, then, at minimum, the rest of \
the commands will also fail with 424 (Failed Dependency).\
"""
reference = "https://tools.ietf.org/html/rfc4918#section-11.4"

[425]
code = 425
phrase = "Too Early"
class = "4XX Client Error"
description = """
A 425 (Too Early) status code indicates that the server is unwilling \
to risk processing a request that might be replayed.\
"""
reference = "https://tools.ietf.org/html/rfc8470#section-5.2"

[426]
code = 426
phrase = "Upgrade Required"
class = "4XX Client Error"
description = """
The 426 (Upgrade Required) status code indicates that 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. The server MUST send an Upgrade header field in a 426 \
response to indicate the required protocol(s).\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.5.15"

[428]
code = 428
phrase = "Precondition Required"
class = "4XX Client Error"
description = """
The 428 status code indicates that the origin server requires the \
request to be conditional.\
"""
reference = "https://tools.ietf.org/html/rfc6585#section-3"

[429]
code = 429
phrase = "Too Many Requests"
class = "4XX Client Error"
description = """
The 429 status code indicates that the user has sent too many \
requests in a given amount of time ("rate limiting").\
"""
reference = "https://tools.ietf.org/html/rfc6585#section-4"

[431]
code = 431
phrase = "Request Header Fields Too Large"
class = "4XX Client Error"
description = """
The 431 status code indicates that the server is unwilling to process \
the request because its header fields are too large. The request MAY \
be resubmitted after reducing the size of the request header fields.\
"""
reference = "https://tools.ietf.org/html/rfc6585#section-5"

[451]
code = 451
phrase = "Unavailable For Legal Reasons"
class = "4XX Client Error"
description = """
This status code indicates that the server is denying access to the \
resource as a consequence of a legal demand.\
"""
reference = "https://tools.ietf.org/html/rfc7725#section-3"

[500]
code = 500
phrase = "Internal Server Error"
class = "5XX Server Error"
description = """
The 500 (Internal Server Error) status code indicates that the server \
encountered an unexpected condition that prevented it from fulfilling \
the request.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.6.1"

[501]
code = 501
phrase = "Not Implemented"
class = "5XX Server Error"
description = """
The 501 (Not Implemented) status code indicates that the server does \
not support the functionality required to fulfill the request. This \
is the appropriate response when the server does not recognize the \
request method and is not capable of supporting it for any resource.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.6.2"

[502]
code = 502
phrase = "Bad Gateway"
class = "5XX Server Error"
description = """
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 accessed while attempting to fulfill the request.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.6.3"

[503]
code = 503
phrase = "Service Unavailable"
class = "5XX Server Error"
description = """
The 503 (Service Unavailable) status code indicates that the server \
is currently unable to handle the request due to a temporary overload \
or scheduled maintenance, which will likely be alleviated after some \
delay. The server MAY send a Retry-After header field \
to suggest an appropriate amount of time for the \
client to wait before retrying the request.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.6.4"

[504]
code = 504
phrase = "Gateway Timeout"
class = "5XX Server Error"
description = """
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 needed to access in order to complete the \
request.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.6.5"

[505]
code = 505
phrase = "HTTP Version Not Supported"
class = "5XX Server Error"
description = """
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 the request message. The server is indicating \
that it is unable or unwilling to complete the request using the same \
major version as the client other than with this error message. \
The server 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.\
"""
reference = "https://tools.ietf.org/html/rfc7231#section-6.6.6"

[506]
code = 506
phrase = "Variant Also Negotiates"
class = "5XX Server Error"
description = """
The 506 status code indicates that the server has an internal \
configuration error: 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.\
"""
reference = "https://tools.ietf.org/html/rfc2295#section-8.1"

[507]
code = 507
phrase = "Insufficient Storage"
class = "5XX Server Error"
description = """
The 507 (Insufficient Storage) status code means the method could not \
be performed on the resource because the server is unable to store \
the representation needed to successfully complete the request. This \
condition is 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 requested by a separate user \
action.\
"""
reference = "https://tools.ietf.org/html/rfc4918#section-11.5"

[508]
code = 508
phrase = "Loop Detected"
class = "5XX Server Error"
description = """
The 508 (Loop Detected) status code indicates that the server \
terminated an operation because it encountered an infinite loop while \
processing a request with "Depth: infinity". This status indicates \
that the entire operation failed.\
"""
reference = "https://tools.ietf.org/html/rfc5842#section-7.2"

[510]
code = 510
phrase = "Not Extended"
class = "5XX Server Error"
description = """
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 extended request. It is outside the scope \
of this specification to specify how the extensions inform the \
client.\
"""
reference = "https://tools.ietf.org/html/rfc2774#section-7"

[511]
code = 511
phrase = "Network Authentication Required"
class = "5XX Server Error"
description = """
The 511 status code indicates that the client needs to authenticate \
to gain network access.\
"""
reference = "https://tools.ietf.org/html/rfc6585#section-6"