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://mojolicio.us');
$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!');
});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($chunk);Read and process data client-side.
client_write
my $chunk = $tx->client_write;Write data client-side.
keep_alive
my $success = $tx->keep_alive;Check if connection can be kept alive.
server_leftovers
my $leftovers = $tx->server_leftovers;Leftovers from the request, used for pipelining server-side.
server_read
$tx->server_read($chunk);Read and process data server-side.
server_write
my $chunk = $tx->server_write;Write data server-side.