| 1 | Revision history for AnyEvent::HTTP |
1 | Revision history for AnyEvent::HTTP |
| 2 | |
2 | |
| 3 | TODO: provide lwp_request function that takes an lwp http requets and returns a http response. |
3 | TODO: provide lwp_request function that takes an lwp http requets and returns a http response. |
| 4 | TODO: httpbis: $location = URI->new_abs($location, "$scheme://$host:$port$path_query")->as_string; |
4 | TODO: httpbis: $location = URI->new_abs($location, "$scheme://$host:$port$path_query")->as_string; |
|
|
5 | TODO: set_proxy hook |
|
|
6 | TODO: use proxy hook |
|
|
7 | |
|
|
8 | 2.13 Wed Jul 27 17:53:58 CEST 2011 |
|
|
9 | - garbled chunked responses caused AnyEvent::HTTP to malfunction |
|
|
10 | (patch by Dmitri Melikyan). |
|
|
11 | - fix GET => HEAD in one case in the documentation (James Bromberger). |
|
|
12 | |
|
|
13 | 2.12 Tue Jun 14 07:22:54 CEST 2011 |
|
|
14 | - fix a possible 'Can't call method "destroyed"' error (which would |
|
|
15 | have been reported by Carl Chambers). |
|
|
16 | |
|
|
17 | 2.11 Tue May 10 14:33:28 CEST 2011 |
|
|
18 | - the keepalive session cache wouldn't take port and scheme into account |
|
|
19 | when reusing connection - potentially causing information leaks |
|
|
20 | (reported by Nick Kostirya). |
|
|
21 | - bump AnyEvent dependency version (reported by Richard Harris). |
| 5 | |
22 | |
| 6 | 2.1 Thu Feb 24 13:11:51 CET 2011 |
23 | 2.1 Thu Feb 24 13:11:51 CET 2011 |
| 7 | - the keepalive and persistent parameters were actually named |
24 | - the keepalive and persistent parameters were actually named |
| 8 | differently in the code - they now work as documented. |
25 | differently in the code - they now work as documented. |
| 9 | - fix a bug where callbacks would sometimes never be called when |
26 | - fix a bug where callbacks would sometimes never be called when |
| 10 | the request timeout is near or below the persistent conenction |
27 | the request timeout is near or below the persistent connection |
| 11 | timeout (testcase by Cindy Wang). |
28 | timeout (testcase by Cindy Wang). |
| 12 | - destroying the guard would have no effect when a request was |
29 | - destroying the guard would have no effect when a request was |
| 13 | recursing or being retired. |
30 | recursing or being retired. |
| 14 | |
31 | |
| 15 | 2.04 Sat Feb 19 07:45:24 CET 2011 |
32 | 2.04 Sat Feb 19 07:45:24 CET 2011 |
