| … | |
… | |
| 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 |
