[Varnish] #905: Modification of multi-line beresp or resp header mangles value
Ken Brownfield
kbrownfield at google.com
Mon Apr 18 21:53:49 CEST 2011
Your back-end is emitting this broken header, but you seem to expect both
nginx and Varnish to understand it. This isn't a bug in nginx, this is an
unfixable behavior problem of your backend, IMHO.
Also, your regex is seemingly replacing ",\s+" with ", ", which is
essentially a NOP. The regex does not (and cannot) address the spurious
newline -- NL is not in \s, and the regex is not multi-line.
Finally, this is definitely not a Varnish bug. Perhaps the code in your app
or plone is manually adding the errant NL.
--
kb
On Mon, Apr 18, 2011 at 07:58, Varnish <varnish-bugs at varnish-cache.org>wrote:
> 9 RxHeader b Vary: X-Anonymous,
> 9 RxHeader b Accept-Encoding
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-bugs/attachments/20110418/4770b4e6/attachment.html>
More information about the varnish-bugs
mailing list