Security Advisories (10)
CPANSA-Mojolicious-2022-03 (2022-12-10)

Mojo::DOM did not correctly parse <script> tags.

CPANSA-Mojolicious-2021-02 (2021-06-01)

Small sessions could be used as part of a brute-force attack to decode the session secret.

CVE-2021-47208 (2021-03-16)

A bug in format detection can potentially be exploited for a DoS attack.

CVE-2018-25100 (2018-02-13)

Mojo::UserAgent::CookieJar leaks old cookies because of the missing host_only flag on empty domain.

CPANSA-Mojolicious-2015-01 (2015-02-02)

Directory traversal on Windows

CPANSA-Mojolicious-2018-03 (2018-05-19)

Mojo::UserAgent was not checking peer SSL certificates by default.

CVE-2020-36829 (2020-11-10)

Mojo::Util secure_compare can leak the string length. By immediately returning when the two strings are not the same length, the function allows an attacker to guess the length of the secret string using timing attacks.

CPANSA-Mojolicious-2018-02 (2018-05-11)

GET requests with embedded backslashes can be used to access local files on Windows hosts

CPANSA-Mojolicious-2014-01 (2014-10-07)

Context sensitivity of method param could lead to parameter injection attacks.

CVE-2024-58134 (2025-05-03)

Mojolicious versions from 0.999922 for Perl uses a hard coded string, or the application's class name, as a HMAC session secret by default. These predictable default secrets can be exploited to forge session cookies. An attacker who knows or guesses the secret could compute valid HMAC signatures for the session cookie, allowing them to tamper with or hijack another user's session.

NAME

Mojolicious::Renderer - MIME type based renderer

SYNOPSIS

use Mojolicious::Renderer;

my $renderer = Mojolicious::Renderer->new;
push @{$renderer->classes}, 'MyApp::Foo';
push @{renderer->paths}, '/home/sri/templates';

DESCRIPTION

Mojolicious::Renderer is the standard Mojolicious renderer.

See Mojolicious::Guides::Rendering for more.

ATTRIBUTES

Mojolicious::Renderer implements the following attributes.

cache

my $cache = $renderer->cache;
$renderer = $renderer->cache(Mojo::Cache->new);

Renderer cache, defaults to a Mojo::Cache object.

classes

my $classes = $renderer->classes;
$renderer   = $renderer->classes(['main']);

Classes to use for finding templates in DATA sections, first one has the highest precedence, defaults to main.

# Add another class with templates in DATA section
push @{$renderer->classes}, 'Mojolicious::Plugin::Fun';

default_format

my $default = $renderer->default_format;
$renderer   = $renderer->default_format('html');

The default format to render if format is not set in the stash. The renderer will use "types" in Mojolicious to look up the content MIME type.

default_handler

my $default = $renderer->default_handler;
$renderer   = $renderer->default_handler('ep');

The default template handler to use for rendering in cases where auto detection doesn't work, like for inline templates.

encoding

my $encoding = $renderer->encoding;
$renderer    = $renderer->encoding('koi8-r');

Will encode the content if set, defaults to UTF-8.

handlers

my $handlers = $renderer->handlers;
$renderer    = $renderer->handlers({epl => sub {...}});

Registered handlers.

helpers

my $helpers = $renderer->helpers;
$renderer   = $renderer->helpers({url_for => sub {...}});

Registered helpers.

paths

my $paths = $renderer->paths;
$renderer = $renderer->paths(['/home/sri/templates']);

Directories to look for templates in, first one has the highest precedence.

# Add another "templates" directory
push @{$renderer->paths}, '/home/sri/templates';

METHODS

Mojolicious::Renderer inherits all methods from Mojo::Base and implements the following ones.

new

my $renderer = Mojolicious::Renderer->new;

Construct a new renderer and register data, json as well as text handlers.

add_handler

$renderer = $renderer->add_handler(epl => sub {...});

Register a new handler.

add_helper

$renderer = $renderer->add_helper(url_for => sub {...});

Register a new helper.

get_data_template

my $template = $renderer->get_data_template({
  template       => 'foo/bar',
  format         => 'html',
  handler        => 'epl'
}, 'foo.html.ep');

Get a DATA section template by name, usually used by handlers.

render

my ($output, $type) = $renderer->render(Mojolicious::Controller->new);
my ($output, $type) = $renderer->render(Mojolicious::Controller->new, {
  template => 'foo/bar',
  foo      => 'bar'
});

Render output through one of the Mojo renderers. This renderer requires some configuration, at the very least you will need to have a default format and a default handler as well as a template or text/json. See "render" in Mojolicious::Controller for a more user-friendly interface.

template_name

my $template = $renderer->template_name({
  template => 'foo/bar',
  format   => 'html',
  handler  => 'epl'
});

Builds a template name based on an options hash reference with template, format and handler, usually used by handlers.

template_path

my $path = $renderer->template_path({
  template => 'foo/bar',
  format   => 'html',
  handler  => 'epl'
});

Builds a full template path based on an options hash reference with template, format and handler, usually used by handlers.

SEE ALSO

Mojolicious, Mojolicious::Guides, http://mojolicio.us.