| … | |
… | |
| 6 | |
6 | |
| 7 | - hopefully fully upgraded to HTTP/1.1. |
7 | - hopefully fully upgraded to HTTP/1.1. |
| 8 | - use more differentiated status 59x codes. |
8 | - use more differentiated status 59x codes. |
| 9 | - ignore leading zeroes in http version. |
9 | - ignore leading zeroes in http version. |
| 10 | - much improved cookie implementation: |
10 | - much improved cookie implementation: |
|
|
11 | - properly implement cookie expiry (for new cookies). |
|
|
12 | - new function to expire cookies and sessions: cookie_jar_expire. |
| 11 | - add special exception to parse broken expires= keys in |
13 | - add special exception to parse broken expires= keys in |
| 12 | set-cookie headers. |
14 | set-cookie headers. |
| 13 | - do not quote cookie values when not strictly necessary, to |
15 | - do not quote cookie values when not strictly necessary, to |
| 14 | improve compatibility with broken servers. |
16 | improve compatibility with broken servers. |
| 15 | - accept and send lots of invalid cookie values exactly as |
17 | - accept and send lots of invalid cookie values exactly as |
| 16 | they were received - this should not impact valid values. |
18 | they were received - this should not impact valid values. |
| 17 | - lowercase cookie parameter names for improved compatibility. |
19 | - lowercase cookie parameter names for improved compatibility. |
| 18 | - support the max-age cookie parameter, used if expires is missing. |
20 | - support the max-age cookie parameter, used if expires is missing. |
| 19 | - properly implement cookie expiry. |
|
|
| 20 | - support cookie dates in parse_date. |
21 | - support cookie dates (and a few others) in parse_date. |
| 21 | |
22 | |
| 22 | 1.5 Fri Dec 31 04:47:08 CET 2010 |
23 | 1.5 Fri Dec 31 04:47:08 CET 2010 |
| 23 | - bugfix: after headers were received, if any error occured the wrong |
24 | - bugfix: after headers were received, if any error occured the wrong |
| 24 | (server-sent) Status and Reason fields would be passed to the callback. |
25 | (server-sent) Status and Reason fields would be passed to the callback. |
| 25 | - when an error occurs during transfer, preserve status/reason. |
26 | - when an error occurs during transfer, preserve status/reason. |
