Search results for "dist:HTTP-Throwable HTTP::Status"
HTTP::Throwable::Role::Status::Gone - 410 Gone
The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user appro...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::Found - 302 Found
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Contr...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::NotFound - 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::UseProxy - 305 Use Proxy
The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origi...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::SeeOther - 303 See Other
The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource....
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::Conflict - 409 Conflict
The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body ...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::ImATeapot - 418 I'm a teapot
This exception provides RFC2324 support, in accordance with section 2.3.3: Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout. Boolean attributes "short" and "...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::Forbidden - 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it S...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::BadRequest - 400 Bad Request
The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications....
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::BadGateway - 502 Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request....
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::NotModified - 304 Not Modified
If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by t...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::Unauthorized - 401 Unauthorized
The request requires user authentication. The response MUST include a WWW-Authenticate header field containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field. If the requ...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::NotAcceptable - 406 Not Acceptable
The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request. Unless it was a HEAD request, the response SHOULD include an...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::LengthRequired - 411 Length Required
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....
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::GatewayTimeout - 504 Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::RequestTimeout - 408 Request Timeout
The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time....
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::NotImplemented - 501 Not Implemented
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....
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::MultipleChoices - 300 Multiple Choices
The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven negotiation information is being provided so that the user (or user agent) can select a preferred representation and redi...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::TooManyRequests - 429 Too Many Requests
The 429 status code indicates that the user has sent too many requests in a given amount of time ("rate limiting"). The response representations SHOULD include details explaining the condition, and MAY include a Retry-After header indicating how to w...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC
HTTP::Throwable::Role::Status::MovedPermanently - 301 Moved Permanently
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or...
RJBS/HTTP-Throwable-0.028 - 31 Dec 2022 21:39:07 UTC