AnyEvent-HTTP
view release on metacpan or search on metacpan
the finish callback with an error code of C<598>).
This callback is useful, among other things, to quickly reject unwanted
content, which, if it is supposed to be rare, can be faster than first
doing a C<HEAD> request.
The downside is that cancelling the request makes it impossible to re-use
the connection. Also, the C<on_header> callback will not receive any
trailer (headers sent after the response body).
Example: cancel the request unless the content-type is "text/html".
on_header => sub {
$_[0]{"content-type"} =~ /^text\/html\s*(?:;|$)/
},
=item on_body => $callback->($partial_body, $headers)
When specified, all body data will be passed to this callback instead of
to the completion callback. The completion callback will get the empty
string instead of the body data.
It has to return either true (in which case AnyEvent::HTTP will continue),
or false, in which case AnyEvent::HTTP will cancel the download (and call
598).
This callback is useful, among other things, to quickly reject
unwanted content, which, if it is supposed to be rare, can be
faster than first doing a "HEAD" request.
The downside is that cancelling the request makes it impossible
to re-use the connection. Also, the "on_header" callback will
not receive any trailer (headers sent after the response body).
Example: cancel the request unless the content-type is
"text/html".
on_header => sub {
$_[0]{"content-type"} =~ /^text\/html\s*(?:;|$)/
},
on_body => $callback->($partial_body, $headers)
When specified, all body data will be passed to this callback
instead of to the completion callback. The completion callback
will get the empty string instead of the body data.
It has to return either true (in which case AnyEvent::HTTP will
continue), or false, in which case AnyEvent::HTTP will cancel
the download (and call the completion callback with an error
( run in 2.028 seconds using v1.01-cache-2.11-cpan-524268b4103 )