RFC 2068:Hypertext Transfer Protocol -- HTTP/1.1
RFC-Ref

LF


Click on the red underlined text to get to the source

... US-ASCII CR, carriage return (13)> LF = <US-ASCII LF, linefeed (10)> ...
... LF = <US-ASCII LF, linefeed (10)> SP = <US-ASCII ...
... HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity ...
... CRLF = CR LF HTTP/1.1 ...


... transport of text media with plain CR or LF alone representing a line break when it is done consistently for an entire entity-body. HTTP ...
... applications MUST accept CRLF, bare CR, and bare LF as being representative of a line break in text media received via HTTP ...
... character set that does not use octets 13 and 10 for CR and LF respectively, as is the case for some multi-byte character sets, HTTP ...
... character set to represent the equivalent of CR and LF for line breaks. This flexibility regarding line breaks ...
... entity-body; a bare CR or LF MUST NOT be substituted for CRLF within any of the HTTP control ...


... elements are separated by SP characters. No CR or LF are allowed except in the final CRLF sequence. ...


... SP characters. No CR or LF is allowed except in the final CRLF sequence. ...
... Reason-Phrase = *<TEXT, excluding CR, LF> HTTP ...


... However, we recommend that applications, when parsing such headers, recognize a single LF as a line terminator and ignore the leading CR. ...
... line breaks as CRLF and forbids the use of CR or LF outside of line break sequences. HTTP ...
... CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted over HTTP ...
... character sets which do not use octets 13 and 10 to represent CR and LF, as is the case for some multi-byte character sets. ...



Google
Web
RFC-Ref