| … | |
… | |
| 200 | Currently, if your proxy requires authorization, you have to specify an |
200 | Currently, if your proxy requires authorization, you have to specify an |
| 201 | appropriate "Proxy-Authorization" header in every request. |
201 | appropriate "Proxy-Authorization" header in every request. |
| 202 | |
202 | |
| 203 | Note that this module will prefer an existing persistent connection, |
203 | Note that this module will prefer an existing persistent connection, |
| 204 | even if that connection was made using another proxy. If you need to |
204 | even if that connection was made using another proxy. If you need to |
| 205 | ensure that a new conneciton is made in this case, you can either force |
205 | ensure that a new connection is made in this case, you can either force |
| 206 | C<persistent> to false or e.g. use the proxy address in your C<sessionid>. |
206 | C<persistent> to false or e.g. use the proxy address in your C<sessionid>. |
| 207 | |
207 | |
| 208 | =item body => $string |
208 | =item body => $string |
| 209 | |
209 | |
| 210 | The request body, usually empty. Will be sent as-is (future versions of |
210 | The request body, usually empty. Will be sent as-is (future versions of |
| … | |
… | |
| 272 | to do this, but you can provide your own C<tcp_connect> function - |
272 | to do this, but you can provide your own C<tcp_connect> function - |
| 273 | obviously, it has to follow the same calling conventions, except that it |
273 | obviously, it has to follow the same calling conventions, except that it |
| 274 | may always return a connection guard object. |
274 | may always return a connection guard object. |
| 275 | |
275 | |
| 276 | The connections made by this hook will be treated as equivalent to |
276 | The connections made by this hook will be treated as equivalent to |
| 277 | connecitons made the built-in way, specifically, they will be put into |
277 | connections made the built-in way, specifically, they will be put into |
| 278 | and taken from the persistent conneciton cache. If your C<$tcp_connect> |
278 | and taken from the persistent connection cache. If your C<$tcp_connect> |
| 279 | function is incompatible with this kind of re-use, consider switching off |
279 | function is incompatible with this kind of re-use, consider switching off |
| 280 | C<persistent> connections and/or providing a C<sessionid> identifier. |
280 | C<persistent> connections and/or providing a C<sessionid> identifier. |
| 281 | |
281 | |
| 282 | There are probably lots of weird uses for this function, starting from |
282 | There are probably lots of weird uses for this function, starting from |
| 283 | tracing the hosts C<http_request> actually tries to connect, to (inexact |
283 | tracing the hosts C<http_request> actually tries to connect, to (inexact |
