AnyEvent-HTTP
view release on metacpan or search on metacpan
=item headers => hashref
The request headers to use. Currently, C<http_request> may provide its own
C<Host:>, C<Content-Length:>, C<Connection:> and C<Cookie:> headers and
will provide defaults at least for C<TE:>, C<Referer:> and C<User-Agent:>
(this can be suppressed by using C<undef> for these headers in which case
they won't be sent at all).
You really should provide your own C<User-Agent:> header value that is
appropriate for your program - I wouldn't be surprised if the default
AnyEvent string gets blocked by webservers sooner or later.
Also, make sure that your headers names and values do not contain any
embedded newlines.
=item timeout => $seconds
The time-out to use for various stages - each connect attempt will reset
the timeout, as will read or write activity, i.e. this is not an overall
timeout.
headers => hashref
The request headers to use. Currently, "http_request" may
provide its own "Host:", "Content-Length:", "Connection:" and
"Cookie:" headers and will provide defaults at least for "TE:",
"Referer:" and "User-Agent:" (this can be suppressed by using
"undef" for these headers in which case they won't be sent at
all).
You really should provide your own "User-Agent:" header value
that is appropriate for your program - I wouldn't be surprised
if the default AnyEvent string gets blocked by webservers sooner
or later.
Also, make sure that your headers names and values do not
contain any embedded newlines.
timeout => $seconds
The time-out to use for various stages - each connect attempt
will reset the timeout, as will read or write activity, i.e.
this is not an overall timeout.
( run in 0.617 second using v1.01-cache-2.11-cpan-49f99fa48dc )