Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

web::dispatch::httpmethods(3pm) [debian man page]

Web::Dispatch::HTTPMethods(3pm) 			User Contributed Perl Documentation			   Web::Dispatch::HTTPMethods(3pm)

NAME
Web::Dispatch::HTTPMethods - Helpers to make RESTFul Dispatchers Easier SYNOPSIS
package MyApp:WithHTTPMethods; use Web::Simple; use Web::Dispatch::HTTPMethods; sub as_text { [200, ['Content-Type' => 'text/plain'], [$_[0]->{REQUEST_METHOD}, $_[0]->{REQUEST_URI}] ] } sub dispatch_request { sub (/get) { GET { as_text(pop) } }, sub (/get-head) { GET { as_text(pop) } HEAD { [204,[],[]] }, }, sub (/get-post-put) { GET { as_text(pop) } ## NOTE: no commas separating http methods POST { as_text(pop) } PUT { as_text(pop) } }, } DESCRIPTION
Exports the most commonly used HTTP methods as subroutine helps into your Web::Simple based application. Additionally adds an automatic HTTP code 405 "Method Not Allow" if none of the HTTP methods match for a given dispatch and also adds a dispatch rule for "HEAD" if no "HEAD" exists but a "GET" does (in which case the "HEAD" returns the "GET" dispatch with an empty body.) We also add at the end of the chain support for the OPTIONS method (if you do not add one yourself. This defaults to http 200 ok + Allows http headers. Also we try to set correct HTTP headers such as "Allows" as makes sense based on your dispatch chain. The following dispatch chains are basically the same: sub dispatch_request { sub (/get-http-methods) { GET { [200, ['Content-Type' => 'text/plain'], ['Hello World']] } }, sub(/get-classic) { sub (GET) { [200, ['Content-Type' => 'text/plain'], ['Hello World']] }, sub (HEAD) { [200, ['Content-Type' => 'text/plain'], []] }, sub (OPTIONS) { [200, ['Content-Type' => 'text/plain', Allows=>'GET,HEAD,OPTIONS'], []]; }, sub () { [405, ['Content-Type' => 'text/plain', Allows=>'GET,HEAD,OPTIONS'], ['Method Not Allowed']] }, } } The idea here is less boilerplate to distract the reader from the main point of the code and also to encapsulate some best practices. NOTE You currently cannot mix http method style and prototype sub style in the same scope, as in the following example: sub dispatch_request { sub (/get-head) { GET { ... } sub (HEAD) { ... } }, } If you try this our code will notice and issue a "die". If you have a good use case please bring it to the authors. EXPORTS This automatically exports the following subroutines: GET PUT POST HEAD DELETE OPTIONS AUTHOR
See Web::Simple for AUTHOR CONTRIBUTORS
See Web::Simple for CONTRIBUTORS COPYRIGHT
See Web::Simple for COPYRIGHT LICENSE
See Web::Simple for LICENSE perl v5.14.2 2012-05-07 Web::Dispatch::HTTPMethods(3pm)

Check Out this Related Man Page

Mojo::Message::Response(3pm)				User Contributed Perl Documentation			      Mojo::Message::Response(3pm)

NAME
Mojo::Message::Response - HTTP 1.1 response container SYNOPSIS
use Mojo::Message::Response; # Parse my $res = Mojo::Message::Reponse->new; $res->parse("HTTP/1.0 200 OKx0ax0d"); $res->parse("Content-Length: 12x0ax0dx0ax0d"); $res->parse("Content-Type: text/plainx0ax0dx0ax0d"); $res->parse('Hello World!'); say $res->body; # Build my $res = Mojo::Message::Response->new; $res->code(200); $res->headers->content_type('text/plain'); $res->body('Hello World!'); say $res->to_string; DESCRIPTION
Mojo::Message::Response is a container for HTTP 1.1 responses as described in RFC 2616. EVENTS
Mojo::Message::Response inherits all events from Mojo::Message. ATTRIBUTES
Mojo::Message::Response inherits all attributes from Mojo::Message and implements the following new ones. "code" my $code = $res->code; $res = $res->code(200); HTTP response code. "message" my $message = $res->message; $res = $res->message('OK'); HTTP response message. METHODS
Mojo::Message::Response inherits all methods from Mojo::Message and implements the following new ones. "cookies" my $cookies = $res->cookies; $res = $res->cookies(Mojo::Cookie::Response->new); $res = $res->cookies({name => 'foo', value => 'bar'}); Access response cookies, usually Mojo::Cookie::Response objects. say $res->cookies->[1]->value; "default_message" my $message = $res->default_message; Generate default response message for code. "fix_headers" $res = $res->fix_headers; Make sure response has all required headers for the current HTTP version. "is_status_class" my $success = $res->is_status_class(200); Check response status class. SEE ALSO
Mojolicious, Mojolicious::Guides, <http://mojolicio.us>. perl v5.14.2 2012-09-05 Mojo::Message::Response(3pm)
Man Page