On 18 April 2011 17:01, 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 Varnish
> [1] and Nginx [2] which may then ma
On 18 April 2011 19:36, Tres Seaver 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
>> behavio
-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
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 note
