Age | Commit message (Collapse) | Author | |
---|---|---|---|
2006-11-25 | Venkat Akella found out that libcurl did not like HTTP responses that simply | Daniel Stenberg | |
responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring. | |||
2005-06-03 | Andres Garcia's text mode fix for the 'data' part | Daniel Stenberg | |
2005-05-11 | Modified the default HTTP headers used by libcurl: | Daniel Stenberg | |
A) Normal non-proxy HTTP: - no more "Pragma: no-cache" (this only makes sense to proxies) B) Non-CONNECT HTTP request over proxy: - "Pragma: no-cache" is used (like before) - "Proxy-Connection: Keep-alive" (for older style 1.0-proxies) C) CONNECT HTTP request over proxy: - "Host: [name]:[port]" - "Proxy-Connection: Keep-alive" | |||
2004-11-11 | Fix behaviour when passing NULL to CURLOPT_POSTFIELDS and CURLOPT_HTTPPOST. | Daniel Stenberg | |