[Web-SIG] WSGI and long response header values

Robert Brewer fumanchu at amor.org
Sat Sep 9 07:51:49 CEST 2006

James Y Knight wrote:
> I don't see what's wrong with encoding with the 75-char
> word-limit, separating "words" by spaces, *without* newlines.
> If the server feels like folding a long line into two, it
> can do so, but it's perfectly within its rights not to,
> and AFAIK nothing at all requires it to ever fold, given
> that a folded line is exactly equivalent to a single space.
> Line folding is one of those things that really has no purpose
> in HTTP besides to write out the examples in the RFCs.

And I just said:
> I was hoping that too, but the server is actually *not*
> within its rights to leave out the newlines, because that
> restriction is actually part of RFC 2047 (MIME headers),
> not the HTTP spec.

Bah. Of course, any HTTP server or proxy is free to unfold headers. So maybe the dream of arbitrary header values via MIME-encoding is broken from the get-go.

Robert Brewer
System Architect
Amor Ministries
fumanchu at amor.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/web-sig/attachments/20060908/e530b86f/attachment.html 

More information about the Web-SIG mailing list