In a previous episode Joe Touch said...
::
::
:: Does anyone recall if HTTP requires translation
:: of CR/LF into LFs? Or are text (or postscript, in this case)
:: files supposed to be transmitted 'as seen' (e.g., binary mode)?
::
:: (seems like our server appears to be doing 'text mode FTP'-like
:: translations, which is a significant performance hog.)
::
you're free to stop doing them..
Request for Comments: 2616
[..]
3.7.1 Canonicalization and Text Defaults
Internet media types are registered with a canonical form. An
entity-body transferred via HTTP messages MUST be represented in the
appropriate canonical form prior to its transmission except for
"text" types, as defined in the next paragraph.
When in canonical form, media subtypes of the "text" type use CRLF as
the text line break. HTTP relaxes this 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-body. HTTP
applications MUST accept CRLF, bare CR, and bare LF as being
representative of a line break in text media received via HTTP. In
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, HTTP allows the use of whatever octet
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 within any of the HTTP control
structures (such as header fields and multipart boundaries).
[..]
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST