----- Original Message ----- From: "Dieter Maurer" <dieter@handshake.de> To: "Gilles Lenfant" <gilles@pilotsystems.net> Cc: <zope@zope.org> Sent: Thursday, July 10, 2003 8:19 PM Subject: Re: [Zope] Apache 2 : stuck fixing content-length HTTP header
Gilles Lenfant wrote at 2003-7-9 21:30 +0200:
This is not - strictly speaking - a Zope problem, but perhaps it's a fixed issue for some of you.
When using the standard RewriteRule scheme with a VirtualHost monster, Apache 2 removes the "content-length" HTTP header from the response provided by Zope.
The "Content-Length" header is quite essential...
What about a bug report for Apache 2?
Hi Dieter, After a quick investigation, I found reports about this in the Apache 2 bugzilla. Cocoon users found that bug too... http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15859 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18757 The headers returned by Zope... <headers> server : Zope/(Zope 2.6.1 (source release, python 2.1, linux2), python 2.1.3, freebsd4) ZServer/1.1b1 content-type : application/pdf accept-ranges : bytes date : Wed, 09 Jul 2003 18:33:13 GMT etag : connection : close last-modified : Wed, 09 Jul 2003 16:44:09 GMT content-length : 25218 </headers> The headers for the same object published through Apache 2... <headers> server : Zope/(Zope 2.6.1 (source release, python 2.1, linux2), python 2.1.3, freebsd4) ZServer/1.1b1 content-type : application/pdf accept-ranges : bytes date : Wed, 09 Jul 2003 18:33:13 GMT etag : connection : close last-modified : Wed, 09 Jul 2003 16:44:09 GMT </headers> Till this is not fixed, I advise Zope hosting admins to continue serving through Apache 1.3.xx Cheers --Gilles