| 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: http://efl20.com/wp-register.php refresh-header, instead of location |
4 | TODO: http://efl20.com/wp-register.php refresh-header, instead of location |
| 5 | TODO: GET => POST like mozilla does it, not like the rfc does it? |
5 | |
| 6 | TODO: maybe support broken Expires header? |
6 | TODO: maybe support broken Expires header? |
|
|
7 | - new "tcp_connect" parameter. |
|
|
8 | |
|
|
9 | 1.46 Mon Sep 6 08:29:34 CEST 2010 |
|
|
10 | - some (broken) servers differentiate between empty search parts |
|
|
11 | and nonexistant search parts, work around this (problem |
|
|
12 | analyzed by Sergey Zasenko). |
|
|
13 | - possibly increase robustness by always setting an on_error |
|
|
14 | callback on the AnyEvent::Handle object (especially in case |
|
|
15 | of user errors, such as nehative timeouts). |
|
|
16 | - we now always follow 301/302/303 redirects and mutate POST to GET. |
|
|
17 | - we now always follow 307 redirects, even for POST. |
|
|
18 | - header-less responses are not parsed correctly (at a negative |
|
|
19 | speed penatly :). |
| 7 | |
20 | |
| 8 | 1.45 Wed Jun 16 21:15:26 CEST 2010 |
21 | 1.45 Wed Jun 16 21:15:26 CEST 2010 |
| 9 | - fix a bug where the handle woudl go away directly after a successful |
22 | - fix a bug where the handle would go away directly after a successful |
| 10 | connect (analyzed and patch by Maxim Dounin). |
23 | connect (analyzed and patch by Maxim Dounin). |
| 11 | - due to popular demand, introduce the Redirect pseudo response header. |
24 | - due to popular demand, introduce the Redirect pseudo response header. |
| 12 | - document URL pseudo-header better. |
25 | - document URL pseudo-header better. |
| 13 | - explain how to implement DNS caching. |
26 | - explain how to implement DNS caching. |
| 14 | |
27 | |
