Bug 18940 - [CURL] Allow \n as line terminator for headers
Summary: [CURL] Allow \n as line terminator for headers
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
Depends on:
Reported: 2008-05-08 10:31 PDT by Marco Barisione
Modified: 2008-05-25 07:37 PDT (History)
1 user (show)

See Also:

Support both \r\n and \n as header delimiter (1.84 KB, patch)
2008-05-08 11:50 PDT, Marco Barisione
alp: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Barisione 2008-05-08 10:31:13 PDT
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.
Comment 1 Marco Barisione 2008-05-08 11:50:35 PDT
Created attachment 21024 [details]
Support both \r\n and \n as header delimiter
Comment 2 Alp Toker 2008-05-25 07:37:53 PDT
Landed in r34126.