| 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 | TODO: ip6 literals in url |
|
|
8 | TODO: maybe read big chunks in smaller portions for chunked-encoding + on_body. |
|
|
9 | TODO: request body is deleted on POST, but might need to be used later for redirects. |
|
|
10 | TODL: on_upgrade, for 101 responses? |
|
|
11 | |
|
|
12 | - add lots of known idempotent methods from httpbis. |
|
|
13 | |
|
|
14 | 2.15 Wed Nov 14 23:22:07 CET 2012 |
|
|
15 | - use the recurse parameter to also limit the number of retries to be |
|
|
16 | done, avodiing endless loops with broken servers, as reported |
|
|
17 | by Carl Chambers. |
|
|
18 | |
|
|
19 | 2.14 Sun Apr 22 14:57:51 CEST 2012 |
|
|
20 | - Time::Local::timegm croaks on out-of-range values. Don't let |
|
|
21 | this disturb AnyEvent::HTTP (reported by: tell me, I forgot...). |
|
|
22 | |
|
|
23 | 2.13 Wed Jul 27 17:53:58 CEST 2011 |
|
|
24 | - garbled chunked responses caused AnyEvent::HTTP to malfunction |
|
|
25 | (patch by Dmitri Melikyan). |
|
|
26 | - fix GET => HEAD in one case in the documentation (James Bromberger). |
|
|
27 | |
|
|
28 | 2.12 Tue Jun 14 07:22:54 CEST 2011 |
|
|
29 | - fix a possible 'Can't call method "destroyed"' error (which would |
|
|
30 | have been reported by Carl Chambers). |
| 5 | |
31 | |
| 6 | 2.11 Tue May 10 14:33:28 CEST 2011 |
32 | 2.11 Tue May 10 14:33:28 CEST 2011 |
| 7 | - the keepalive session cache wouldn't take port and scheme into account |
33 | - the keepalive session cache wouldn't take port and scheme into account |
| 8 | when reusing connection - potentially causing information leaks |
34 | when reusing connection - potentially causing information leaks |
| 9 | (reported by Nick Kostirya). |
35 | (reported by Nick Kostirya). |
