[Zope-dev] Re: ZServer response RFC compliance improvement

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jens Vagelpohl wrote:

> I'd like to get the zserver-content-length.patch createed by dunny in 
> this collector issue:
> 
> http://www.zope.org/Collectors/Zope/1866/collector_issue_contents
> 
> merged into the Zope 2.7/2.8 branches and the trunk. It ensures that 
> certain classes of responses (e.g. 304) correctly leave out the 
> content-length header. Can anyone seee a valid reason for not merging 
> it in?

Are we sure that we won't be breaking the rather large possible set of
installed servers running behind Apache 1.3.x with the bug for which
adding the content length was a workaround?  If the header only affects
Safari / Konqueror (in practice), then this is *not* a pure win, if
there are a significant number of affected servers in production.

We should probably look at adding a zope.conf switch for this behavior,
and leave the header in place by default for 2.7.x and 2.8.x.  We could
default it off for the trunk, with a commented-out entry showing how
(and why) to reenable it, and deprecate that setting through 2.10 or
something.


Tres.
- --
===================================================================
Tres Seaver          +1 202-558-7113          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDCNvf+gerLs4ltQ4RAmKVAJsF1l/+962zjvpS6EdQz5OHZ1LPtwCguI0D
SyOAlav7XSbe7r+B2Wum+MI=
=Zs8U
-----END PGP SIGNATURE-----