view release on metacpan or  search on metacpan

site/config.html  view on Meta::CPAN

every request.  
<font face="courier new" size=3><pre>
</pre></font>From an application deployment standpoint, you
also gain the ability to deploy your application as a 
snapshot taken when the server starts and restarts.
This provides you with the reassurance that during a
production server update from development sources, you 
do not have to worry with sources being used for the 
wrong libraries and such, while they are all being 
copied over.
<font face="courier new" size=3><pre>
</pre></font>Finally, though you really should not do this, you can
work on a live production application, with a test server
reloading changes, but your production server does see
the changes until you restart or stop/start it.  This 
saves your public from syntax errors while you are just
doing a quick bug fix.
<font face="courier new" size=3><pre>
  PerlSetVar StatScripts 1
</pre></font>
	
	<p>
	<a name=SoftRedirect></a>
	<font face=verdana><font class=title size=-1 color=#555555><b>SoftRedirect</b></font>
<font face="courier new" size=3><pre>
</pre></font>default 0, if true, a $Response-&gt;Redirect() does not end the 
script.  Normally, when a Redirect() is called, the script
is ended automatically.  SoftRedirect 1, is a standard
way of doing redirects, allowing for html output after the 
redirect is specified.
<font face="courier new" size=3><pre>
  PerlSetVar SoftRedirect 0
</pre></font>
	
	<p>
	<a name=Filter></a>
	<font face=verdana><font class=title size=-1 color=#555555><b>Filter</b></font>
<font face="courier new" size=3><pre>
</pre></font>On/Off, default Off.  With filtering enabled, you can take advantage of 
full server side includes (<a href=ssi.html><font size=-1 face=verdana><b>SSI</b></font></a>), implemented through Apache::SSI.  
SSI is implemented through this mechanism by using Apache::Filter.  
A sample configuration for full SSI with filtering is in the 
<a href=eg/.htaccess>./site/eg/.htaccess</a> file, with a relevant example script <a href=eg/ssi_filter.ssi>./site/eg/ssi_filter.ssi</a>.
<font face="courier new" size=3><pre>
</pre></font>You may only use this option with modperl v1.16 or greater installed
and PERL_STACKED_HANDLERS enabled.  Filtering may be used in 
conjunction with other handlers that are also &quot;filter aware&quot;.
If in doubt, try building your <a href=http://perl.apache.org><font size=-1 face=verdana><b>mod_perl</b></font></a> with 
<font face="courier new" size=3><pre>
  perl Makefile.PL EVERYTHING=1
</pre></font>With filtering through Apache::SSI, you should expect near a
a 20% performance decrease.
<font face="courier new" size=3><pre>
  PerlSetVar Filter Off
</pre></font>
	
	<p>
	<a name=CgiHeaders></a>
	<font face=verdana><font class=title size=-1 color=#555555><b>CgiHeaders</b></font>
<font face="courier new" size=3><pre>
</pre></font>default 0.  When true, script output that looks like HTTP / <a href=cgi.html><font size=-1 face=verdana><b>CGI</b></font></a>
headers, will be added to the HTTP headers of the request.
So you could add:
<font face="courier new" size=3><pre>  Set-Cookie: test=message

  &lt;html&gt;...
</pre></font>to the top of your script, and all the headers preceding a newline
will be added as if with a call to $Response-&gt;AddHeader().  This
functionality is here for compatibility with raw cgi scripts,
and those used to this kind of coding.
<font face="courier new" size=3><pre>
</pre></font>When set to 0, CgiHeaders style headers will not be parsed from the 
script response.
<font face="courier new" size=3><pre>
  PerlSetVar CgiHeaders 0
</pre></font>
	
	<p>
	<a name=Clean></a>
	<font face=verdana><font class=title size=-1 color=#555555><b>Clean</b></font>
<font face="courier new" size=3><pre>
</pre></font>default 0, may be set between 1 and 9.  This setting determine how much
text/html output should be compressed.  A setting of 1 strips mostly
white space saving usually 10% in output size, at a performance cost
of less than 5%.  A setting of 9 goes much further saving anywhere
25% to 50% typically, but with a performance hit of 50%.
<font face="courier new" size=3><pre>
</pre></font>This config option is implemented via HTML::Clean.  Per script
configuration of this setting is available via the $Response-&gt;{Clean}
property, which may also be set between 0 and 9.
<font face="courier new" size=3><pre>
  PerlSetVar Clean 0
</pre></font>
	
	<p>
	<a name=CompressGzip></a>
	<font face=verdana><font class=title size=-1 color=#555555><b>CompressGzip</b></font>
<font face="courier new" size=3><pre>
</pre></font>default 0, if true will gzip compress HTML output on the
fly if Compress::Zlib is installed, and the client browser
supports it.  Depending on the HTML being compressed, 
the client may see a 50% to 90% reduction in HTML output.
I have seen 40K of HTML squeezed down to just under 6K.
This will come at a 5%-20% hit to CPU usage per request
compressed.
<font face="courier new" size=3><pre>
</pre></font>Note there are some cases when a browser says it will accept
gzip encoding, but then not render it correctly.  This
behavior has been seen with IE5 when set to use a proxy but 
not using a proxy, and the URL does not end with a .html or .htm.
No work around has yet been found for this case so use at your 
own risk.
<font face="courier new" size=3><pre>
  PerlSetVar CompressGzip 1
</pre></font>
	
	<p>
	<a name=FormFill></a>
	<font face=verdana><font class=title size=-1 color=#555555><b>FormFill</b></font>
<font face="courier new" size=3><pre>
</pre></font>default 0, if true will auto fill HTML forms with values