Catalyst::Plugin::PageCache - Cache the output of entire pages

        use Catalyst;
        MyApp->setup( qw/Cache::FileCache PageCache/ );

            'Plugin::PageCache' => {
                expires => 300,
                set_http_headers => 1,
                auto_cache => [
                debug => 1,
                # Optionally, a cache hook to be called prior to dispatch to
                # determine if the page should be cached.  This is called both
                # before dispatch, and before finalize.
                cache_hook => 'some_method'
    sub some_method {
            my $c = shift;
            if ( $c->user_exists and $c->user->some_field ) {
                return 0; # Don't cache
            return 1; # Cache

        # in a controller method
        $c->cache_page( '3600' );

        $c->clear_cached_page( '/list' );

        # Expire at a specific time
        $c->cache_page( $datetime_object );

        # Fine control
            last_modified   => $last_modified,
            cache_seconds   => 24 * 60 * 60,    # once a day
            expires         => 300,             # allow client caching

    Many dynamic websites perform heavy processing on most pages, yet this
    information may rarely change from request to request. Using the
    PageCache plugin, you can cache the full output of different pages so
    they are served to your visitors as fast as possible. This method of
    caching is very useful for withstanding a Slashdotting, for example.

    This plugin requires that you also load a Cache plugin. Please see the
    Known Issues when choosing a cache backend.

    PageCache should be placed at the end of your plugin list.

    You should only use the page cache on pages which have NO user-specific
    or customized content. Also, be careful if caching a page which may
    forward to another controller. For example, if you cache a page behind a
    login screen, the logged-in version may be cached and served to
    unauthenticated users.

    Note that pages that result from POST requests will never be cached.

    On my Athlon XP 1800+ Linux server, a cached page is served in 0.008
    seconds when using the HTTP::Daemon server and any of the Cache plugins.

    Configuration is optional. You may define the following configuration

        expires => $seconds

    This will set the default expiration time for all page caches. If you do
    not specify this, expiration defaults to 300 seconds (5 minutes).

        cache_headers => 1

    Enable this value if you need your cached responses to include custom
    HTTP headers set by your application. This may be necessary if you
    operate behind an edge cache such as Akamai. This option is disabled by

        set_http_headers => 1

    Enabling this value will cause Catalyst to set the correct HTTP headers
    to allow browsers and proxy servers to cache your page. This will
    further reduce the load on your server. The headers are set in such a
    way that the browser/proxy cache will expire at the same time as your
    cache. The Last-Modified header will be preserved if you have already
    specified it. This option is disabled by default.

        auto_cache => [

    To automatically cache certain pages, or all pages, you can specify
    auto-cache URIs as an array reference. Any controller within your
    application that matches one of the auto_cache URIs will be cached using
    the default expiration time. URIs may be specified as absolute: '/list'
    or as a regex: '/view/.*'

        disable_index => 1

    In order to support the "clear_cached_page" method, PageCache keeps an
    index of all cached pages. If you don't intend to use
    "clear_cached_page", you may enable this config option to avoid the
    overhead of creating and updating the cache index. This option is
    disabled by default.

        busy_lock => 10

    On a high traffic site where page re-generation may take many seconds, a
    common problem encountered is the "dog-pile" effect, where many
    concurrent connections all hit a page where the cache has expired and
    all perform the same expensive operation to rebuild the cache. To
    prevent this situation, you can set the busy_lock option to the maximum
    number of seconds any of your pages can be expected to take to rebuild
    the cache. Then, when the cache expires, the first request will rebuild
    the cache while also extending the expiration time by the number of
    seconds specified, allowing other requests that arrive before the cache
    has been rebuilt to use the previously cached page. This option is
    disabled by default.

        debug => 1

    This will print additional debugging information to the Catalyst log.
    You will need to have -Debug enabled to see these messages. You can also
    specify an optional config parameter auto_check_user. If this option is
    enabled, automatic caching is disabled for logged in users.

        cache_hook => 'cache_hook_method'

    Calls a method on the application that is expected to return a true or
    false. This method is called before dispatch, and before finalize so you
    can short circuit the pagecache behavior. As an example, if you want to
    disable PageCache while running under debug mode:

        package MyApp;
    sub cache_hook_method { return shift->debug; }

    Or, if you want to not cache for certain roles, say "admin":

        sub cache_hook_method {
            my ( $c ) = @_;
            return !$c->check_user_roles('admin');

    Note that this is called BEFORE auto_check_user, so you have more
    flexibility to determine what to do for not logged in users.

    To override the generation of page keys:

            'Plugin::PageCache' => {
                key_maker => sub {
                    my $c = shift;
                    return $c->req->base . '/' . $c->req->path;

    Call cache_page in any controller method you wish to be cached.

        $c->cache_page( $expire );

    The page will be cached for $expire seconds. Every user who visits the
    URI(s) referenced by that controller will receive the page directly from
    cache. Your controller will not be processed again until the cache
    expires. You can set this value to as low as 60 seconds if you have
    heavy traffic to greatly improve site performance.

    Pass in a DateTime object to make the cache expire at a given point in

        $two_hours = DateTime->now->add( hours => 2 );
        $c->cache_page( $two_hours );

    The page will be stored in the page cache until this time.

    If set_http_headers is set then Expires and Cache-Control headers will
    also be set to expire at the given date as well.

    Pass in a list or hash reference for finer control.

            last_modified   => $last_modified,
            cache_seconds   => 24 * 60 * 60,
            expires         => 30,

    This allows separate control of the page cache and the header cache
    values sent to the client.

    Possible options are:

        Last modified time in epoch seconds. If not set will use either the
        current Last-Modified header, or if not set, the current time.

        This is the number of seconds to keep the page in the page cache,
        which may be different (normally longer) than the time that client
        caches may store the page.

        This is the lenght of time in seconds that a client may cache the
        page before revalidating (by asking the server if the document has

        Unlike above, this is a fixed setting that each client will see.
        Regardless of how much longer the page will be cached in the page
        cache the client still sees the same expires time.

        Setting zero (0) for expires will result in the page being cached,
        but headers will be sent telling the client to not cache the page.
        Allows caching expensive content to generate, but any changes will
        be seen right away.

    To clear the cached value for a URI, you may call clear_cached_page.

        $c->clear_cached_page( '/view/userlist' );
        $c->clear_cached_page( '/view/.*' );

    This method takes an absolute path or regular expression. For obvious
    reasons, this must be called from a different controller than the cached
    controller. You may for example wish to build an admin page that lets
    you clear page caches.

    Note that clear_cached_page will generate a warning if disable_index is

    "dispatch" decides whether or not to serve a particular request from the

    "finalize" caches the result of the current request if needed.

    "setup" initializes all default values.

    If your application uses Catalyst::Plugin::I18N for localization, a
    separate cache key will be used for each language a page is displayed

    It is not currently possible to cache pages served from the Static
    plugin. If you're concerned enough about performance to use this plugin,
    you should be serving static files directly from your web server anyway.

    Cache::FastMmap does not have the ability to specify different
    expiration times for cached data. Therefore, if your
    MyApp->config->{cache}->{expires} value is set to anything other than 0,
    you may experience problems with the clear_cached_page method, because
    the cache index may be removed. For best results, you may wish to use
    Cache::FileCache or Cache::Memcached as your cache backend.

    Catalyst, Catalyst::Plugin::Cache::FastMmap,
    Catalyst::Plugin::Cache::FileCache, Catalyst::Plugin::Cache::Memcached

    Andy Grundman, <>

    Bill Moseley, <>, for many patches and tests.

    Roberto HenrÃquez, <>, for i18n support.

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