Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   5388 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

Apache::PerlRunFilter(User Contributed Perl DocumentatApache::PerlRunFilter(3)

NAME
       Apache::PerlRunFilter - run Perl scripts in an Apache::Filter chain

SYNOPSIS
	#in httpd.conf

	PerlModule Apache::PerlRunFilter

	# Run the output of scripts through Apache::SSI
	<Files ~ "\.pl$">
	 SetHandler perl-script
	 PerlHandler Apache::PerlRunFilter Apache::SSI
	 PerlSetVar Filter on
	</Files>

	# Generate some Perl code using templates, then execute it
	<Files ~ "\.tmpl$">
	 SetHandler perl-script
	 PerlHandler YourModule::GenCode Apache::PerlRunFilter
	 PerlSetVar Filter on
	</Files>

DESCRIPTION
       This module is a subclass of Apache::PerlRun, and contains all of its
       functionality.  The only difference between the two is that this module
       can be used in conjunction with the Apache::Filter module, whereas
       Apache::PerlRun cannot.

       It only takes a tiny little bit of code to make the filtering stuff
       work, so perhaps it would be more appropriate for the code to be inte-
       grated right into Apache::PerlRun.  As it stands, I've had to duplicate
       a bunch of PerlRun's code here (in the handler routine), so bug fixes &
       feature changes must be made both places.

CAVEATS
       Note that this is not an exact replacement for Apache::Registry - it
       doesn't do any of the code-caching stuff that Registry does.  It
       shouldn't be too hard a task, but for now Registry is still based on
       old code, and Doug's plan is to make future versions of Registry by
       subclassing PerlRun (see Apache::RegistryNG).  Since this is the case,
       I figured I'd hold off on doing any Registry work until things have
       moved forward a bit.

SEE ALSO
       perl(1), mod_perl(3), Apache::PerlRun(3)

AUTHOR
       Ken Williams <ken@forum.swarthmore.edu>

perl v5.8.8			  2005-09-25	      Apache::PerlRunFilter(3)

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome