Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

plack::app::urlmap(3pm) [debian man page]

Plack::App::URLMap(3pm) 				User Contributed Perl Documentation				   Plack::App::URLMap(3pm)

NAME
Plack::App::URLMap - Map multiple apps in different paths SYNOPSIS
use Plack::App::URLMap; my $app1 = sub { ... }; my $app2 = sub { ... }; my $app3 = sub { ... }; my $urlmap = Plack::App::URLMap->new; $urlmap->map("/" => $app1); $urlmap->map("/foo" => $app2); $urlmap->map("http://bar.example.com/" => $app3); my $app = $urlmap->to_app; DESCRIPTION
Plack::App::URLMap is a PSGI application that can dispatch multiple applications based on URL path and hostnames (a.k.a "virtual hosting") and takes care of rewriting "SCRIPT_NAME" and "PATH_INFO" (See "HOW THIS WORKS" for details). This module is inspired by Rack::URLMap. METHODS
map $urlmap->map("/foo" => $app); $urlmap->map("http://bar.example.com/" => $another_app); Maps URL path or an absolute URL to a PSGI application. The match order is sorted by host name length and then path length. URL paths need to match from the beginning and should match completely till the path separator (or the end of the path). For example, if you register the path "/foo", it will match with the request "/foo", "/foo/" or "/foo/bar" but it won't match with "/foox". Mapping URL with host names is also possible, and in that case the URL mapping works like a virtual host. Mappings will nest. If $app is already mapped to "/baz" it will match a request for "/foo/baz" but not "/foo". See "HOW THIS WORKS" for more details. mount Alias for "map". to_app my $handler = $urlmap->to_app; Returns the PSGI application code reference. Note that the Plack::App::URLMap object is callable (by overloading the code dereference), so returning the object itself as a PSGI application should also work. DEBUGGING
You can set the environment variable "PLACK_URLMAP_DEBUG" to see how this application matches with the incoming request host names and paths. HOW THIS WORKS
This application works by fixing "SCRIPT_NAME" and "PATH_INFO" before dispatching the incoming request to the relocated applications. Say you have a Wiki application that takes "/index" and "/page/*" and makes a PSGI application $wiki_app out of it, using one of supported web frameworks, you can put the whole application under "/wiki" by: # MyWikiApp looks at PATH_INFO and handles /index and /page/* my $wiki_app = sub { MyWikiApp->run(@_) }; use Plack::App::URLMap; my $app = Plack::App::URLMap->new; $app->mount("/wiki" => $wiki_app); When a request comes in with "PATH_INFO" set to "/wiki/page/foo", the URLMap application $app strips the "/wiki" part from "PATH_INFO" and appends that to "SCRIPT_NAME". That way, if the $app is mounted under the root (i.e. "SCRIPT_NAME" is "") with standalone web servers like Starman, "SCRIPT_NAME" is now locally set to "/wiki" and "PATH_INFO" is changed to "/page/foo" when $wiki_app gets called. AUTHOR
Tatsuhiko Miyagawa SEE ALSO
Plack::Builder perl v5.14.2 2011-06-22 Plack::App::URLMap(3pm)

Check Out this Related Man Page

Plack::Middleware::Auth::Basic(3pm)			User Contributed Perl Documentation		       Plack::Middleware::Auth::Basic(3pm)

NAME
Plack::Middleware::Auth::Basic - Simple basic authentication middleware SYNOPSIS
use Plack::Builder; my $app = sub { ... }; builder { enable "Auth::Basic", authenticator => &authen_cb; $app; }; sub authen_cb { my($username, $password) = @_; return $username eq 'admin' && $password eq 's3cr3t'; } DESCRIPTION
Plack::Middleware::Auth::Basic is a basic authentication handler for Plack. CONFIGURATION
authenticator A callback function that takes username and password supplied and returns whether the authentication succeeds. Required. Authenticator can also be an object that responds to "authenticate" method that takes username and password and returns boolean, so backends for Authen::Simple is perfect to use: use Authen::Simple::LDAP; enable "Auth::Basic", authenticator => Authen::Simple::LDAP->new(...); realm Realm name to display in the basic authentication dialog. Defaults to restricted area. LIMITATIONS
This middleware expects that the application has a full access to the headers sent by clients in PSGI environment. That is normally the case with standalone Perl PSGI web servers such as Starman or HTTP::Server::Simple::PSGI. However, in a web server configuration where you can't achieve this (i.e. using your application via Apache's mod_cgi), this middleware does not work since your application can't know the value of "Authorization:" header. If you use Apache as a web server and CGI to run your PSGI application, you can either a) compile Apache with "-DSECURITY_HOLE_PASS_AUTHORIZATION" option, or b) use mod_rewrite to pass the Authorization header to the application with the rewrite rule like following. RewriteEngine on RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L] AUTHOR
Tatsuhiko Miyagawa SEE ALSO
Plack perl v5.14.2 2012-06-21 Plack::Middleware::Auth::Basic(3pm)
Man Page