Re: [Zope-dev] [Zope2] Multiline response headers causing problems for proxies.

2011-04-19 Thread Laurence Rowe
On 18 April 2011 17:01, Laurence Rowe l...@lrowe.co.uk wrote: When using response.appendHeader, Zope appends the new value following an ,\r\n\t which splits the header over multiple lines. While this behaviour is standards compliant, it causes problems for both Varnish [1] and Nginx [2] which

[Zope-dev] [Zope2] Multiline response headers causing problems for proxies.

2011-04-18 Thread Laurence Rowe
When using response.appendHeader, Zope appends the new value following an ,\r\n\t which splits the header over multiple lines. While this behaviour is standards compliant, it causes problems for both Varnish [1] and Nginx [2] which may then mangle the header value. In fact the HTTP 1.0 spec notes

Re: [Zope-dev] [Zope2] Multiline response headers causing problems for proxies.

2011-04-18 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/18/2011 12:01 PM, Laurence Rowe wrote: When using response.appendHeader, Zope appends the new value following an ,\r\n\t which splits the header over multiple lines. While this behaviour is standards compliant, it causes problems for both

Re: [Zope-dev] [Zope2] Multiline response headers causing problems for proxies.

2011-04-18 Thread Laurence Rowe
On 18 April 2011 19:36, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/18/2011 12:01 PM, Laurence Rowe wrote: When using response.appendHeader, Zope appends the new value following an ,\r\n\t which splits the header over multiple lines. While