Bug 18940

Summary: [CURL] Allow \n as line terminator for headers
Product: WebKit Reporter: Marco Barisione <marco.barisione>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: alp
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Support both \r\n and \n as header delimiter alp: review+

Marco Barisione
Reported 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.
Attachments
Support both \r\n and \n as header delimiter (1.84 KB, patch)
2008-05-08 11:50 PDT, Marco Barisione 		alp: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Marco Barisione
Comment 1 2008-05-08 11:50:35 PDT
Created attachment 21024 [details] Support both \r\n and \n as header delimiter
Alp Toker
Comment 2 2008-05-25 07:37:53 PDT
Landed in r34126.
Note You need to log in before you can comment on or make changes to this bug.