The curl back-end allows only CRLF as line terminator for the headers, causing troubles with some web pages like http://www.thinkgeek.com/geektoys/warfare/69de/ From the HTTP standard: The line terminator for message-header fields is the sequence CRLF. However, we recommend that applications, when parsing such headers, recognize a single LF as a line terminator and ignore the leading CR I will write a patch ASAP.
Created attachment 21024 [details] Support both \r\n and \n as header delimiter
Landed in r34126.