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

CR


Click on the red underlined text to get to the source

... control character (octets 0 - 31) and DEL (127)> CR = <US-ASCII CR, carriage return (13)> ...
... CR = <US-ASCII CR, carriage return (13)> LF = <US-ASCII ...
... HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements ...
... CRLF = CR LF ...


... requirement and allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an entire entity ...
... HTTP applications MUST accept CRLF, bare CR, and bare LF as being representative of a line break ...
... addition, if the text is represented in a 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 ...
... sequences are defined by that character set to represent the equivalent of CR and LF for line breaks. This flexibility regarding ...
... line breaks applies only to text media in the entity-body; a bare CR or LF MUST NOT be substituted for CRLF ...


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


... element separated by SP characters. No CR or LF is allowed except in the final CRLF ...
... extension-code = 3DIGIT Reason-Phrase = *<TEXT, excluding CR, LF> ...


... headers, recognize a single LF as a line terminator and ignore the leading CR. The character set ...
... "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line break ...
... line break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break ...
... allows the use of some 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