Closed
Bug 228334
Opened 21 years ago
Closed 9 years ago
http parser should accept single LF as a substitute for CRLF
Categories
(Core :: Networking, enhancement)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: info, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5b) Gecko/20030829 Camino/0.7+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5b) Gecko/20030829 Camino/0.7+
please try and load this page using camino. http://software.oxalyn.com/aemonitor/
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•21 years ago
|
||
Sorry, but it doesn't load in IE 6 either. Not a Mozilla bug.
Not a Build Config bug in any event.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Comment 2•21 years ago
|
||
It loads in my IE6.0.something...
From a quick HTTP log, the server is not sending CRLF properly at the end of
header lines, probably just LF; so we parse the entire request as one giant
header line, which obviously fails.
From the HTTP/1.1 spec section 19.3
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.
Status: RESOLVED → UNCONFIRMED
Component: Build Config → Networking: HTTP
Resolution: INVALID → ---
Updated•21 years ago
|
Assignee: nobody → darin
Severity: normal → enhancement
QA Contact: build-config → httpqa
Summary: web page will not load at all (blank white page) . Loads in other browsers. You suck! :) → http parser should accept single LF as a substitute for CRLF
Benjamin: can you post a log snippet showing this? if so, please set status=NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•21 years ago
|
||
benc: the log just shows that moz is parsing all the headers and body of this
page as one giant (meaningless) header.
Comment 5•19 years ago
|
||
-> default owner
Assignee: darin → nobody
Component: Networking: HTTP → Networking
QA Contact: networking.http → networking
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 21 years ago → 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•