plack::middleware::lighttpdscriptnamefix(3pm) [debian man page]

Plack::Middleware::LighttpdScriptNameFix(3pm)		User Contributed Perl Documentation	     Plack::Middleware::LighttpdScriptNameFix(3pm)

NAME

       Plack::Middleware::LighttpdScriptNameFix - fixes wrong SCRIPT_NAME and PATH_INFO that lighttpd sets

SYNOPSIS

	 # in your app.psgi
	 use Plack::Builder;

	 builder {
	   enable "LighttpdScriptNameFix";
	   $app;
	 };

	 # Or from the command line
	 plackup -s FCGI -e 'enable "LighttpdScriptNameFix"' /path/to/app.psgi

DESCRIPTION

       This middleware fixes wrong "SCRIPT_NAME" and "PATH_INFO" set by lighttpd when you mount your app under the root path ("/"). If you use
       lighttpd 1.4.23 or later you can instead enable "fix-root-scriptname" flag inside "fastcgi.server" instead of using this middleware.

CONFIGURATION

       script_name
	   Even with "fix-root-scriptname", lighttpd still sets weird "SCRIPT_NAME" and "PATH_INFO" if you mount your application at "" or
	   something that ends with "/". Setting "script_name" option tells the middleware how to reconstruct the new correct "SCRIPT_NAME" and
	   "PATH_INFO".

	   If you mount the app under "/something/", you should set:

	     enable "LighttpdScriptNameFix", script_name => "/something";

	   and when a request for "/something/a/b?param=1" comes, "SCRIPT_NAME" becomes "/something" and "PATH_INFO" becomes "/a/b".

	   "script_name" option is set to empty by default, which means all the request path is set to "PATH_INFO" and it behaves like your
	   fastcgi application is mounted in the root path.

AUTHORS

       Yury Zavarin

       Tatsuhiko Miyagawa

SEE ALSO

       Plack::Handler::FCGI <http://github.com/miyagawa/Plack/issues#issue/68> <https://redmine.lighttpd.net/issues/729>

perl v5.14.2							    2011-02-27			     Plack::Middleware::LighttpdScriptNameFix(3pm)

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)