Zope sends malformed Vary header
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope 2 |
Fix Released
|
Medium
|
Martijn Pieters |
Bug Description
From http://
"""
We have a proxy that checks the web site before allowing access, and if there is a mistake, we can't connect to your web site.
Your web site answers as a vary accept-encoding which is normal, but the next value is not correct. The line return for this Vary is "\n" instead of being "\r\n".
"""
Wichert adds:
"""
From ZPublisher.
key = name.lower()
if accumulate_
return
Notice how that uses \n
"""
This seems to be an issue in Zope. I'm not sure what the specs say, but it seems like both \r\n is required here.
Full case history:
And on IRC, Wichert added:
"HTTP RFCs say headers are \r\n seperated"
:)