[ViewVC] Diff of: cvs/AnyEvent-HTTP/HTTP.pm

Comparing AnyEvent-HTTP/HTTP.pm (file contents):
Revision 1.68 by root, Fri Dec 31 19:22:18 2010 UTC vs.
Revision 1.69 by root, Fri Dec 31 19:32:47 2010 UTC

 =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 for C<TE:>, C<Referer:> and C<User-Agent:> (this can
+will provide defaults at least for C<TE:>, C<Referer:> and C<User-Agent:>
-be suppressed by using C<undef> for these headers in which case they won't
+(this can be suppressed by using C<undef> for these headers in which case
-be sent at all).
+they won't be sent at all).
 =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
 Note that this cookie implementation is not of very high quality, nor
 meant to be complete. If you want complete cookie management you have to
 do that on your own. C<cookie_jar> is meant as a quick fix to get some
 cookie-using sites working. Cookies are a privacy disaster, do not use
 them unless required to.
+When cookie processing is enabled, the C<Cookie:> and C<Set-Cookie:>
+headers will be ste and handled by this module, otherwise they will be
+left untouched.
 =item tls_ctx => $scheme | $tls_ctx
 Specifies the AnyEvent::TLS context to be used for https connections. This
 parameter follows the same rules as the C<tls_ctx> parameter to

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines