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
-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
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
This is the summary for test reports received on the
zope-tests list between 2011-04-17 00:00:00 UTC and 2011-04-18 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
