Prancer::Const
use Prancer::Const; sub handle { my $self = shift; mount('GET', '/', sub { ... context->finalize(Prancer::Const::OK); }); dispatch; }
Alias for Prancer::Const::HTTP_OK.
Prancer::Const::HTTP_OK
Alias for Prancer::Const::HTTP_MOVED_TEMPORARILY.
Prancer::Const::HTTP_MOVED_TEMPORARILY
Alias for Prancer::Const::HTTP_UNAUTHORIZED.
Prancer::Const::HTTP_UNAUTHORIZED
Alias for Prancer::Const::HTTP_FORBIDDEN.
Prancer::Const::HTTP_FORBIDDEN
Alias for Prancer::Const::HTTP_NOT_FOUND.
Prancer::Const::HTTP_NOT_FOUND
Alias for Prancer::Const::HTTP_INTERNAL_SERVER_ERROR.
Prancer::Const::HTTP_INTERNAL_SERVER_ERROR
This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).
Expect: 100-continue
100 Continue
417 Expectation Failed
This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
The request has been fulfilled and resulted in a new resource being created.
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.
The server successfully processed the request, but is returning information that may be from another source.
The server successfully processed the request, but is not returning any content. Usually used as a response to a successful delete request.
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
The server is delivering only part of the resource due to a range header sent by the client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.
This and all future requests should be directed to the given URI.
This is an example of industry practice contradicting the standard. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviors. However, some Web applications and frameworks use the 302 status code as if it were the 303.
This is the same as Prancer::Const::HTTP_MOVED_TEMPORARILIY.
Prancer::Const::HTTP_MOVED_TEMPORARILIY
The response to the request can be found under another URI using a GET method. When received in response to a POST (or PUT/DELETE), it should be assumed that the server has received the data and the redirect should be issued with a separate GET message
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-Match. This means that there is no need to retransmit the resource, since the client still has a previously downloaded copy.
The requested resource is only available through a proxy, whose address is provided in the response. Many HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.
In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For instance, a POST request should be repeated using another POST request.
The request, and all future requests should be repeated using another URI. 307 and 308 (as proposed) parallel the behaviors of 302 and 301, but do not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.
The request cannot be fulfilled due to bad syntax.
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.
403 Forbidden
WWW-Authenticate
Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code is not usually used. YouTube uses this status if a particular IP address has made excessive requests, and requires the person to enter a CAPTCHA.
The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference. On servers where authentication is required, this commonly means that the provided credentials were successfully authenticated but that the credentials still do not grant the client permission to access the resource (e.g., a recognized user attempting to access restricted content).
401 Unauthorized
The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
Accept
The client must first authenticate itself with the proxy.
The server timed out waiting for the request. According to W3 HTTP specifications: "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."
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict in the case of multiple updates.
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.
The request did not specify the length of its content, which is required by the requested resource.
The server does not meet one of the preconditions that the requester put on the request.
The request is larger than the server is willing or able to process.
The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request.
The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.
image/svg+xml
The client has asked for a portion of the file, but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file.
The server cannot meet the requirements of the Expect request-header field.
The client should switch to a different protocol such as TLS/1.0.
The origin server requires the request to be conditional. Intended to prevent "the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict."
The user has sent too many requests in a given amount of time. Intended for use with rate limiting schemes.
The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.
A generic error message, given when no more specific message is suitable.
The server either does not recognize the request method, or it lacks the ability to fulfill the request. Usually this implies future availability (e.g., a new feature of a web-service API).
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. Sometimes, this can be permanent as well on test servers.
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
The server does not support the HTTP protocol version used in the request.
This documentation was copied almost entirely from Wikipedia's documentation on HTTP codes and is freely available under Creative Commons Attribution-ShareAlike License.
To install Prancer, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Prancer
CPAN shell
perl -MCPAN -e shell install Prancer
For more information on module installation, please visit the detailed CPAN module installation guide.