catalyst::engine::apache2::mp19(3pm) [debian man page]

Catalyst::Engine::Apache2::MP19(3pm)			User Contributed Perl Documentation		      Catalyst::Engine::Apache2::MP19(3pm)

NAME

       Catalyst::Engine::Apache2::MP19 - Catalyst Apache2 mod_perl 1.99x Engine

SYNOPSIS

	   # Set up your Catalyst app as a mod_perl 1.99x application in httpd.conf
	   PerlSwitches -I/var/www/MyApp/lib

	   # Preload your entire application
	   PerlModule MyApp

	   <VirtualHost *>
	       ServerName    myapp.hostname.com
	       DocumentRoot  /var/www/MyApp/root

	       <Location />
		   SetHandler	       modperl
		   PerlResponseHandler MyApp
	       </Location>

	       # you can also run your app in any non-root location
	       <Location /some/other/path>
		   SetHandler	       perl-script
		   PerlResponseHandler MyApp
	       </Location>

	       # Make sure to let Apache handle your static files
	       # (It is not necessary to remove the Static::Simple plugin
	       # in production; Apache will bypass Static::Simple if
	       # configured in this way)

	       <Location /static>
		   SetHandler	       default-handler
	       </Location>

	       # If not running at a root location in a VirtualHost,
	       # you'll probably need to set an Alias to the location
	       # of your static files, and allow access to this location:

	       Alias /myapp/static /filesystem/path/to/MyApp/root/static
	       <Directory /filesystem/path/to/MyApp/root/static>
		   allow from all
	       </Directory>
	       <Location /myapp/static>
		   SetHandler default-handler
	       </Location>

	   </VirtualHost>

DESCRIPTION

       This is the Catalyst engine specialized for Apache2 mod_perl version 1.99x.

WARNING

       mod_perl 1.99 was the beta version for mod_perl 2.0.  Upgrading to 2.0 is strongly recommended.

CGI ISSUES

       In order to run Catalyst under mod_perl 1.99 you will need to downgrade CGI to version 3.07, as it has dropped support for 1.99 in later
       versions.

ModPerl::Registry
       While this method is not recommended, you can also run your Catalyst application via a ModPerl::Registry script.

       httpd.conf:

	   PerlModule ModPerl::Registry
	   Alias / /var/www/MyApp/script/myapp_registry.pl/

	   <Directory /var/www/MyApp/script>
	       Options +ExecCGI
	   </Directory>

	   <Location />
	       SetHandler	   perl-script
	       PerlResponseHandler ModPerl::Registry
	   </Location>

       script/myapp_registry.pl (you will need to create this):

	   #!/usr/bin/perl

	   use strict;
	   use warnings;
	   use MyApp;

	   MyApp->handle_request( Apache::RequestUtil->request );

METHODS

   ok_constant
SEE ALSO

       Catalyst, Catalyst::Engine, Catalyst::Engine::Apache2.

AUTHORS

       o   Sebastian Riedel <sri@cpan.org>

       o   Christian Hansen <ch@ngmedia.com>

       o   Andy Grundman <andy@hybridized.org>

       o   Tomas Doran <bobtfish@bobtfish.net>

COPYRIGHT AND LICENSE

       This software is copyright (c) 2010 by The "AUTHORS".

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.10.1							    2010-11-26				      Catalyst::Engine::Apache2::MP19(3pm)

Check Out this Related Man Page

Catalyst::Engine::PSGI(3pm)				User Contributed Perl Documentation			       Catalyst::Engine::PSGI(3pm)

NAME

       Catalyst::Engine::PSGI - PSGI engine for Catalyst

SYNOPSIS

	 # app.psgi
	 use strict;
	 use MyApp;

	 MyApp->setup_engine('PSGI');
	 my $app = sub { MyApp->run(@_) };

DESCRIPTION

       Catalyst::Engine::PSGI is a Catalyst Engine that adapts Catalyst into the PSGI gateway protocol.

COMPATIBILITY

       o   Currently this engine works with Catalyst 5.8 (Catamoose) or newer.

       o   Your application is supposed to work with any PSGI servers without any code modifications, but if your application uses
	   "$c->res->write" to do streaming write, this engine will buffer the output until your app finishes.

	   To do real streaming with this engine, you should implement an IO::Handle-like object that responds to "getline" method that returns
	   chunk or undef when done, and set that object to "$c->res->body".

	   Alternatively, it is possible to set the body to a code reference, which will be used to stream content as documented in the PSGI spec.

       o   When your application runs behind the frontend proxy like nginx or lighttpd, this Catalyst engine doesn't automatically recognize the
	   incoming headers like "X-Forwarded-For", because respecting these headers by default causes a potential security issue.

	   You have to enable Plack::Middleware::ReverseProxy or Plack::Middleware::ForwardedHeaders to automatically promote those forwarded
	   headers into "REMOTE_ADDR" hence IP address of the request.

	   ReverseProxy middleware is pretty simple and has no configuration while ForwardedHeaders allows you to configure which upstream host to
	   trust, etc.

AUTHOR

       Tatsuhiko Miyagawa <miyagawa@bulknews.net>

       Most of the code is taken and modified from Catalyst::Engine::CGI.

LICENSE

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

SEE ALSO

       Catalyst::Engine PSGI Plack

perl v5.12.3							    2011-06-11					       Catalyst::Engine::PSGI(3pm)

Linux and UNIX Man Pages

catalyst::engine::apache2::mp19(3pm) [debian man page]

Check Out this Related Man Page