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

Mojo::Transaction::HTTP - HTTP transaction

SYNOPSIS

use Mojo::Transaction::HTTP;

# Client
my $tx = Mojo::Transaction::HTTP->new;
$tx->req->method('GET');
$tx->req->url->parse('http://example.com');
$tx->req->headers->accept('application/json');
say $tx->res->code;
say $tx->res->headers->content_type;
say $tx->res->body;
say $tx->remote_address;

# Server
my $tx = Mojo::Transaction::HTTP->new;
say $tx->req->method;
say $tx->req->url->to_abs;
say $tx->req->headers->accept;
say $tx->remote_address;
$tx->res->code(200);
$tx->res->headers->content_type('text/plain');
$tx->res->body('Hello World!');

DESCRIPTION

Mojo::Transaction::HTTP is a container for HTTP transactions as described in RFC 2616.

EVENTS

Mojo::Transaction::HTTP inherits all events from Mojo::Transaction and can emit the following new ones.

request

$tx->on(request => sub {
  my $tx = shift;
  ...
});

Emitted when a request is ready and needs to be handled.

$tx->on(request => sub {
  my $tx = shift;
  $tx->res->headers->header('X-Bender' => 'Bite my shiny metal ass!');
});

unexpected

$tx->on(unexpected => sub {
  my ($tx, $res) = @_;
  ...
});

Emitted for unexpected 1xx responses that will be ignored.

$tx->on(unexpected => sub {
  my $tx = shift;
  $tx->res->on(finish => sub { say 'Followup response is finished.' });
});

upgrade

$tx->on(upgrade => sub {
  my ($tx, $ws) = @_;
  ...
});

Emitted when transaction gets upgraded to a Mojo::Transaction::WebSocket object.

$tx->on(upgrade => sub {
  my ($tx, $ws) = @_;
  $ws->res->headers->header('X-Bender' => 'Bite my shiny metal ass!');
});

ATTRIBUTES

Mojo::Transaction::HTTP inherits all attributes from Mojo::Transaction.

METHODS

Mojo::Transaction::HTTP inherits all methods from Mojo::Transaction and implements the following new ones.

client_read

$tx->client_read($bytes);

Read data client-side, used to implement user agents.

client_write

my $bytes = $tx->client_write;

Write data client-side, used to implement user agents.

is_empty

my $success = $tx->is_empty;

Check transaction for HEAD request and 1xx, 204 or 304 response.

keep_alive

my $success = $tx->keep_alive;

Check if connection can be kept alive.

server_read

$tx->server_read($bytes);

Read data server-side, used to implement web servers.

server_write

my $bytes = $tx->server_write;

Write data server-side, used to implement web servers.

SEE ALSO

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