ASP4
view release on metacpan or search on metacpan
before deciding whether is should persist its changes in ->save().
[New Features]
- $Session->is_read_only(1) is new. Setting it to a true value (eg: 1) will prevent
the default behavior of calling $Session->save() at the end of each successful request.
2011-04-08 v1.043
- Documentation overhaul.
2011-03-23 v1.042
- Fixed sporadic error in master pages that looks like this:
Can't call method "Write" on an undefined value at /tmp/PAGE_CACHE/BStat/_masters_global_asp.pm line 1.
- Apparently $s->init_asp_objects($context) was not getting called before the
master page's run() method was called, resulting in a call to $Response->Write(...)
before $Response had been initialized.
2010-11-11 v1.041
- ASP4::UserAgent calls all cleanup handlers registered via $Server->RegisterCleanup(sub { }, @args)
at the end of each request, not when the ASP4::Mock::Pool object's DESTROY method is called.
This fixes a condition which caused conflict when a Class::DBI::Lite ORM is
used and the ASP4 application is executed via the `asp4` helper script.
t/010-basic/090-everything.t view on Meta::CPAN
# static 404:
{
ok(
my $res = $api->ua->get('/missing-file.txt'),
"Requested /missing-file.txt"
);
ok(
! $res->is_success,
"Not successful"
);
like $res->status_line, qr{^404}, "Status looks like a 404 error";
}
t/040-round2/010-include-missing.t view on Meta::CPAN
use warnings 'all';
use Test::More 'no_plan';
use ASP4::API;
my $api = ASP4::API->new();
my $res = $api->ua->get("/include-missing.asp");
ok( $res->is_success, "res.is_success" );
like $res->content, qr/Before\s+After/, "res.content looks right";
( run in 0.456 second using v1.01-cache-2.11-cpan-64827b87656 )