FCGI Buffer
1.0.0
FCGI::Buffer - Verify, Cache and Optimise FCGI Output
Version 0.19
FCGI::Buffer verifies the HTML that you produce by passing it through
HTML::Lint.
FCGI::Buffer optimises FCGI programs by reducing, filtering and compressing output to speed up the transmission and by nearly seamlessly making use of client and server caches.
To make use of client caches, that is to say to reduce needless calls to your server asking for the same data:
use FCGI;
use FCGI::Buffer;
# ...
my $request = FCGI::Request();
while($request->FCGI::Accept() >= 0) {
my $buffer = FCGI::Buffer->new();
$buffer->init(
optimise_content => 1,
lint_content => 0,
);
# ...
}
To also make use of server caches, that is to say to save regenerating output when different clients ask you for the same data, you will need to create a cache. But that's simple:
use FCGI;
use CHI;
use FCGI::Buffer;
# ...
my $request = FCGI::Request();
while($request->FCGI::Accept() >= 0) {
my $buffer = FCGI::Buffer->new();
$buffer->init(
optimise_content => 1,
lint_content => 0,
cache => CHI->new(driver => 'File')
);
if($buffer->is_cached()) {
# Nothing has changed - use the version in the cache
$request->Finish();
next;
# ...
}
}
To temporarily prevent the use of server-side caches, for example whilst debugging before publishing a code change, set the NO_CACHE environment variable to any non-zero value. This will also stop ETag being added to the header. If you get errors about Wide characters in print it means that you've forgotten to emit pure HTML on non-ASCII characters. See HTML::Entities. As a hack work around you could also remove accents and the like by using Text::Unidecode, which works well but isn't really what you want.
Create an FCGI::Buffer object. Do one of these for each FCGI::Accept.
Set various options and override default values.
# Put this toward the top of your program before you do anything
# By default, generate_tag, generate_304 and compress_content are ON,
# optimise_content and lint_content are OFF. Set optimise_content to 2 to
# do aggressive JavaScript optimisations which may fail.
use FCGI::Buffer;
my $buffer = FCGI::Buffer->new()->init({
generate_etag => 1, # make good use of client's cache
generate_last_modified => 1, # more use of client's cache
compress_content => 1, # if gzip the output
optimise_content => 0, # optimise your program's HTML, CSS and JavaScript
cache => CHI->new(driver => 'File'), # cache requests
cache_key => 'string', # key for the cache
cache_age => '10 minutes', # how long to store responses in the cache
logger => $self->{logger},
lint_content => 0, # Pass through HTML::Lint
generate_304 => 1, # When appropriate, generate 304: Not modified
save_to => { directory => '/var/www/htdocs/save_to', ttl => 600, create_table => 1 },
info => CGI::Info->new(),
lingua => CGI::Lingua->new(),
});
If no cache_key is given, one will be generated which may not be unique. The cache_key should be a unique value dependent upon the values set by the browser.
The cache object will be an object that understands get_object(), set(), remove() and created_at() messages, such as an CHI object. It is used as a server-side cache to reduce the need to rerun database accesses.
Items stay in the server-side cache by default for 10 minutes. This can be overridden by the cache_control HTTP header in the request, and the default can be changed by the cache_age argument to init().
Save_to is feature which stores output of dynamic pages to your htdocs tree and replaces future links that point to that page with static links to avoid going through CGI at all. Ttl is set to the number of seconds that the static pages are deemed to be live for, the default is 10 minutes. If set to 0, the page is live forever. To enable save_to, a info and lingua arguments must also be given. It works best when cache is also given. Only use where output is guaranteed to be the same with a given set of arguments (the same criteria for enabling generate_304). You can turn it off on a case by case basis thus:
my $params = CGI::Info->new()->params();
if($params->{'send_private_email'}) {
$buffer->init('save_to' => undef);
}
Info is an optional argument to give information about the FCGI environment, e.g. a CGI::Info object.
Logger will be an object that understands debug() such as an Log::Log4perl object.
To generate a last_modified header, you must give a cache object.
Init allows a reference of the options to be passed. So both of these work: use FCGI::Buffer; #... my $buffer = FCGI::Buffer->new(); $b->init(generate_etag => 1); $b->init({ generate_etag => 1, info => CGI::Info->new() });
Generally speaking, passing by reference is better since it copies less on to the stack.
If you give a cache to init() then later give cache => undef, the server side cache is no longer used. This is useful when you find an error condition when creating your HTML and decide that you no longer wish to store the output in the cache.
Synonym for init, kept for historical reasons.
Returns true if the server is allowed to store the results locally. This is the value of X-Cache in the returned header.
Returns true if the output is cached. If it is then it means that all of the expensive routines in the FCGI script can be by-passed because we already have the result stored in the cache.
# Put this toward the top of your program before you do anything
# Example key generation - use whatever you want as something
# unique for this call, so that subsequent calls with the same
# values match something in the cache
use CGI::Info;
use CGI::Lingua;
use FCGI::Buffer;
my $i = CGI::Info->new();
my $l = CGI::Lingua->new(supported => ['en']);
# To use server side caching you must give the cache argument, however
# the cache_key argument is optional - if you don't give one then one will
# be generated for you
my $buffer = FCGI::Buffer->new();
if($buffer->can_cache()) {
$buffer->init(
cache => CHI->new(driver => 'File'),
cache_key => $i->domain_name() . '/' . $i->script_name() . '/' . $i->as_string() . '/' . $l->language()
);
if($buffer->is_cached()) {
# Output will be retrieved from the cache and sent automatically
exit;
}
}
# Not in the cache, so now do our expensive computing to generate the
# results
print "Content-type: text/htmln";
# ...
Nigel Horne,
FCGI::Buffer should be safe even in scripts which produce lots of different output, e.g. e-commerce situations. On such pages, however, I strongly urge to setting generate_304 to 0 and sending the HTTP header "Cache-Control: no-cache".
When using Template, ensure that you don't use it to output to STDOUT, instead you will need to capture into a variable and print that. For example:
my $output;
$template->process($input, $vars, $output) || ($output = $template->error());
print $output;
Can produce buggy JavaScript if you use the