<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Serving documents as application/xhtml+xml without content negotiation</title>
	<link>http://spacergif.net/2006/08/06/serving-documents-as-applicationxhtmlxml-without-content-negotiation/</link>
	<description>Extend your borders!</description>
	<pubDate>Wed, 19 Nov 2008 10:45:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Doug</title>
		<link>http://spacergif.net/2006/08/06/serving-documents-as-applicationxhtmlxml-without-content-negotiation/#comment-5</link>
		<pubDate>Sun, 03 Sep 2006 16:50:44 +0000</pubDate>
		<guid>http://spacergif.net/2006/08/06/serving-documents-as-applicationxhtmlxml-without-content-negotiation/#comment-5</guid>
					<description>You misread the RFC. To quote: 

HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see appendix 19.3 for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described in section 3.7.

       CRLF           = CR LF

HTTP/1.1 header field values can be folded onto multiple lines if the continuation line begins with a space or horizontal tab. All linear white space, including folding, has the same semantics as SP. A recipient MAY replace any linear white space with a single SP before interpreting the field value or forwarding the message downstream.

       LWS            = [CRLF] 1*( SP &amp;#124; HT )

A single \r or \n is not sufficient. The line terminate must be a \r\n.</description>
		<content:encoded><![CDATA[<p>You misread the RFC. To quote: </p>
<p>HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see appendix 19.3 for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described in section 3.7.</p>
<p>       CRLF           = CR LF</p>
<p>HTTP/1.1 header field values can be folded onto multiple lines if the continuation line begins with a space or horizontal tab. All linear white space, including folding, has the same semantics as SP. A recipient MAY replace any linear white space with a single SP before interpreting the field value or forwarding the message downstream.</p>
<p>       LWS            = [CRLF] 1*( SP | HT )</p>
<p>A single \r or \n is not sufficient. The line terminate must be a \r\n.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
