| … | |
… | |
| 342 | =item persistent => $boolean |
342 | =item persistent => $boolean |
| 343 | |
343 | |
| 344 | Try to create/reuse a persistent connection. When this flag is set |
344 | Try to create/reuse a persistent connection. When this flag is set |
| 345 | (default: true for idempotent requests, false for all others), then |
345 | (default: true for idempotent requests, false for all others), then |
| 346 | C<http_request> tries to re-use an existing (previously-created) |
346 | C<http_request> tries to re-use an existing (previously-created) |
| 347 | persistent connection to the host and, failing that, tries to create a new |
347 | persistent connection to same host (i.e. identical URL scheme, hostname, |
| 348 | one. |
348 | port and session) and, failing that, tries to create a new one. |
| 349 | |
349 | |
| 350 | Requests failing in certain ways will be automatically retried once, which |
350 | Requests failing in certain ways will be automatically retried once, which |
| 351 | is dangerous for non-idempotent requests, which is why it defaults to off |
351 | is dangerous for non-idempotent requests, which is why it defaults to off |
| 352 | for them. The reason for this is because the bozos who designed HTTP/1.1 |
352 | for them. The reason for this is because the bozos who designed HTTP/1.1 |
| 353 | made it impossible to distinguish between a fatal error and a normal |
353 | made it impossible to distinguish between a fatal error and a normal |
| … | |
… | |
| 1294 | function from time to time. |
1294 | function from time to time. |
| 1295 | |
1295 | |
| 1296 | A cookie jar is initially an empty hash-reference that is managed by this |
1296 | A cookie jar is initially an empty hash-reference that is managed by this |
| 1297 | module. Its format is subject to change, but currently it is as follows: |
1297 | module. Its format is subject to change, but currently it is as follows: |
| 1298 | |
1298 | |
| 1299 | The key C<version> has to contain C<1>, otherwise the hash gets |
1299 | The key C<version> has to contain C<2>, otherwise the hash gets |
| 1300 | emptied. All other keys are hostnames or IP addresses pointing to |
1300 | cleared. All other keys are hostnames or IP addresses pointing to |
| 1301 | hash-references. The key for these inner hash references is the |
1301 | hash-references. The key for these inner hash references is the |
| 1302 | server path for which this cookie is meant, and the values are again |
1302 | server path for which this cookie is meant, and the values are again |
| 1303 | hash-references. Each key of those hash-references is a cookie name, and |
1303 | hash-references. Each key of those hash-references is a cookie name, and |
| 1304 | the value, you guessed it, is another hash-reference, this time with the |
1304 | the value, you guessed it, is another hash-reference, this time with the |
| 1305 | key-value pairs from the cookie, except for C<expires> and C<max-age>, |
1305 | key-value pairs from the cookie, except for C<expires> and C<max-age>, |
| … | |
… | |
| 1309 | |
1309 | |
| 1310 | Here is an example of a cookie jar with a single cookie, so you have a |
1310 | Here is an example of a cookie jar with a single cookie, so you have a |
| 1311 | chance of understanding the above paragraph: |
1311 | chance of understanding the above paragraph: |
| 1312 | |
1312 | |
| 1313 | { |
1313 | { |
| 1314 | version => 1, |
1314 | version => 2, |
| 1315 | "10.0.0.1" => { |
1315 | "10.0.0.1" => { |
| 1316 | "/" => { |
1316 | "/" => { |
| 1317 | "mythweb_id" => { |
1317 | "mythweb_id" => { |
| 1318 | _expires => 1293917923, |
1318 | _expires => 1293917923, |
| 1319 | value => "ooRung9dThee3ooyXooM1Ohm", |
1319 | value => "ooRung9dThee3ooyXooM1Ohm", |
