| … | |
… | |
| 147 | Whether to recurse requests or not, e.g. on redirects, authentication |
147 | Whether to recurse requests or not, e.g. on redirects, authentication |
| 148 | retries and so on, and how often to do so. |
148 | retries and so on, and how often to do so. |
| 149 | |
149 | |
| 150 | =item headers => hashref |
150 | =item headers => hashref |
| 151 | |
151 | |
| 152 | The request headers to use, with the header name (I<MUST be in lowercase>) |
152 | The request headers to use. Currently, C<http_request> may provide its |
| 153 | as key and header value as hash value. |
153 | own C<Host:>, C<Content-Length:>, C<Connection:> and C<Cookie:> headers |
| 154 | |
154 | and will provide defaults for C<User-Agent:> and C<Referer:> (this can be |
| 155 | Currently, http_request> may provide its own C<host>, C<content-length>, |
|
|
| 156 | C<connection> and C<cookie> headers and will provide defaults for |
|
|
| 157 | C<user-agent> and C<referer> (this can be suppressed by using a value of |
|
|
| 158 | C<undef> for these headers in which case they won't be sent at all). |
155 | suppressed by using C<undef> for these headers in which case they won't be |
|
|
156 | sent at all). |
| 159 | |
157 | |
| 160 | =item timeout => $seconds |
158 | =item timeout => $seconds |
| 161 | |
159 | |
| 162 | The time-out to use for various stages - each connect attempt will reset |
160 | The time-out to use for various stages - each connect attempt will reset |
| 163 | the timeout, as will read or write activity, i.e. this is not an overall |
161 | the timeout, as will read or write activity, i.e. this is not an overall |
