This module is for web application framework developers who currently uses CGI to handle query parameters, and would like for the frameworks to comply with the PSGI protocol. Only slight modifications should be required if the framework is already co...

ASP4 is a great way to build web applications. PSGI/Plack is a great way to abstract a web application from the environment in which it is run. While I wouldn't yet run a high-traffic ASP4 web application in this way, it works very well for smaller t...

Furl::PSGI is a subclass of Furl that requires a PSGI app and sends all requests through that app. This helps facilitate testing, where you can pass a Furl::PSGI rather than a Furl and handle any requests in the same process rather than go out over t...

All action subs are passed a PSGI::Hector object as the only parameter, from this you should be able to reach everything you need....

Allow Labyrinth to run under Plack. Use the PSGI protocol to interface with a Plack web server to process web requests....

This module defines an AS2 Protocol compliant Plack application. The AS2 Protocol is specified by RFC 4130. This protocol defines a secure peer-to-peer data transfer with receipt using HTTP. The receipt is called a Message Disposition Notification (M...

Mojo::Server::PSGI allows Mojolicious applications to run on all PSGI compatible servers. See "DEPLOYMENT" in Mojolicious::Guides::Cookbook for more....

This is where the magic happens for Furl::PSGI, similar to Furl and Furl::HTTP. Given a PSGI app, all requests are sent to it and no network connections should be made....

This module extends CGI::Simple to use in some web applications under the PSGI servers. This is a experimental branch from CGI::PSGI module for CGI by Tatsuhiko Miyagawa....

use CGI::Parse::PSGI qw(parse_cgi_output); my $output = YourApp->run; my $psgi_res = parse_cgi_output(\$output); An option hash can also be passed: my $psgi_res = parse_cgi_output(\$output, \%options);...

This subclass of FCGI::Async allows a FastCGI responder to use a PSGI application to respond to requests. It acts as a gateway between the FastCGI connection from the webserver, and the "PSGI" application. Aside from the use of "PSGI" instead of the ...

If you want a more fully featured PSGI experience, it would be wise to look at the Plack and Starman set of modules. Net::Server::PSGI is intended as an easy gateway into PSGI. But to get the most out of all that PSGI has to offer, you should review ...

Mount PSGI apps inside of WebGUI...

Request ID AWS::Lambda::PSGI injects the request id that compatible with Plack::Middleware::RequestId. env->{'psgix.request_id'} # It is same value with $context->aws_request_id...

This module can be used to convert CGI.pm-compatible HTTP header properties into PSGI response header array reference. This module requires your query class is orthogonal to a global variable %ENV. For example, CGI::PSGI adds the "env" attribute to C...

This is an extension of FCGI::Engine::Core to support PSGI applications. You can refer to the FCGI::Engine docs for most of what you need to know, the only difference being that instead of a "handler_class", "handler_method" and "handler_args" you si...

Abstract class used in all other PSGI::Hector classes....

This module allows an application designed for the CGI environment to run in a PSGI environment, and thus on any of the backends that PSGI supports. It works by translating the environment provided by the PSGI specification to one expected by the CGI...