[Web-SIG] Output header encodings? (was Re: Backup plan: WSGI 1 Addenda and wsgiref update for Py3)

P.J. Eby pje at telecommunity.com
Fri Sep 24 17:06:02 CEST 2010

At 03:48 PM 9/23/2010 -0500, Ian Bicking wrote:
>It only fixes the one case of non-Latin1 characters, there are still 
>many other values you can put into a header (a newline or control 
>character for instance), and innumerable header-specific 
>issues.  It seems to be adding complexity for one of the least 
>problematic cases.

Ok, you found one that convinces me.  ;-)  "Headers are text, bodies 
are bytes" shall be the rule.  I'll rewrite the "note about string 
types" and change the way I'm updating the spec accordingly.

More information about the Web-SIG mailing list