/ 
Plack-1.0008
⭐ Starred 488
/ Plack::Handler
Security Advisories (4)
CPANSA-Plack-2015-0202 (2015-02-02)

Fixed a possible directory traversal with Plack::App::File on Win32.

CPANSA-Plack-2014-0801 (2014-08-01)

Plack::App::File would previously strip trailing slashes off provided paths. This in combination with the common pattern of serving files with Plack::Middleware::Static could allow an attacker to bypass a whitelist of generated files

CPANSA-Plack-2013-0131 (2013-01-31)

Fixed directory traversal bug in Plack::App::File on win32 environments

CVE-2026-7381 (2026-04-29)

Plack::Middleware::XSendfile versions through 1.0053 for Perl can allow client-controlled path rewriting. Plack::Middleware::XSendfile allows the variation setting (sendfile type) to be set by the client via the X-Sendfile-Type header, if it is not considered in the middleware constructor or the Plack environment. A malicious client can set the X-Sendfile-Type header to "X-Accel-Redirect" to services running behind nginx reverse proxies, and then set the X-Accel-Mapping to map the path to an arbitrary file on the server. Since 1.0053, Plack::Middleware::XSendfile is deprecated and will be removed from future releases of Plack. This is similar to CVE-2025-61780 for Rack::Sendfile, although Plack::Middleware::XSendfile has some mitigations that disallow regular expressions to be used in the mapping, and only apply the mapping for the "X-Accel-Redirect" type.

NAME

Plack::Handler - Connects PSGI applications and Web servers

SYNOPSIS

package Plack::Handler::AwesomeWebServer;
sub new {
    my($class, %opt) = @_;
    ...
    return $self;
}

sub run {
    my($self, $app) = @_;
    # launch the AwesomeWebServer and run $app in the loop
}

# then from command line
plackup -s AwesomeWebServer -a app.psgi

DESCRIPTION

Plack::Handler defines an adapter (connector) interface to adapt plackup and Plack::Runner to various PSGI web servers, such as Apache2 for mod_perl and Standalone for HTTP::Server::PSGI.

It is an empty class, and as long as they implement the methods defined as an Server adapter interface, they do not need to inherit Plack::Handler.

If you write a new handler for existing web servers, I recommend you to include the full name of the server module after Plack::Handler prefix, like Plack::Handler::Net::Server::Coro if you write a handler for Net::Server::Coro. That way you'll be using plackup command line option like:

plackup -s Net::Server::Coro

that makes it easy to figure out which web server you're going to use.

METHODS

new
$server = FooBarServer->new(%args);

Creates a new adapter object. %args can take arbitrary parameters to configure server environments but common parameters are:

port

Port number the server listens to.

host

Address the server listens to. Set to undef to listen any interface.

run
$server->run($app);

Starts the server process and when a request comes in, run the PSGI application passed in $app in the loop.

register_service
$server->register_service($app);

Optional interface if your server should run in parallel with other event loop, particularly AnyEvent. This is the same as run but doesn't run the main loop.

SEE ALSO

rackup