… | |
… | |
152 | |
152 | |
153 | =item headers => hashref |
153 | =item headers => hashref |
154 | |
154 | |
155 | The request headers to use. Currently, C<http_request> may provide its own |
155 | The request headers to use. Currently, C<http_request> may provide its own |
156 | C<Host:>, C<Content-Length:>, C<Connection:> and C<Cookie:> headers and |
156 | C<Host:>, C<Content-Length:>, C<Connection:> and C<Cookie:> headers and |
157 | will provide defaults for C<TE:>, C<Referer:> and C<User-Agent:> (this can |
157 | will provide defaults at least for C<TE:>, C<Referer:> and C<User-Agent:> |
158 | be suppressed by using C<undef> for these headers in which case they won't |
158 | (this can be suppressed by using C<undef> for these headers in which case |
159 | be sent at all). |
159 | they won't be sent at all). |
160 | |
160 | |
161 | =item timeout => $seconds |
161 | =item timeout => $seconds |
162 | |
162 | |
163 | The time-out to use for various stages - each connect attempt will reset |
163 | The time-out to use for various stages - each connect attempt will reset |
164 | the timeout, as will read or write activity, i.e. this is not an overall |
164 | the timeout, as will read or write activity, i.e. this is not an overall |
… | |
… | |
192 | Note that this cookie implementation is not of very high quality, nor |
192 | Note that this cookie implementation is not of very high quality, nor |
193 | meant to be complete. If you want complete cookie management you have to |
193 | meant to be complete. If you want complete cookie management you have to |
194 | do that on your own. C<cookie_jar> is meant as a quick fix to get some |
194 | do that on your own. C<cookie_jar> is meant as a quick fix to get some |
195 | cookie-using sites working. Cookies are a privacy disaster, do not use |
195 | cookie-using sites working. Cookies are a privacy disaster, do not use |
196 | them unless required to. |
196 | them unless required to. |
|
|
197 | |
|
|
198 | When cookie processing is enabled, the C<Cookie:> and C<Set-Cookie:> |
|
|
199 | headers will be ste and handled by this module, otherwise they will be |
|
|
200 | left untouched. |
197 | |
201 | |
198 | =item tls_ctx => $scheme | $tls_ctx |
202 | =item tls_ctx => $scheme | $tls_ctx |
199 | |
203 | |
200 | Specifies the AnyEvent::TLS context to be used for https connections. This |
204 | Specifies the AnyEvent::TLS context to be used for https connections. This |
201 | parameter follows the same rules as the C<tls_ctx> parameter to |
205 | parameter follows the same rules as the C<tls_ctx> parameter to |