[Zope] Roxen and incorrect Content-Length: header
Bill Anderson
bill.anderson@libc.org
Wed, 26 Jan 2000 18:21:01 -0700
This is a multi-part message in MIME format.
--------------98581B9F845A5EF32EE19AB2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Bruce Elrick wrote:
>
> Is anyone aware of Roxen+Zope returning incorrect Content-Length: header
> information? I've searched the list archives and found Bill's comment about
> Roxen needing to be patched, but it doesn't indicate where the patch comes
> from, what the bug is (is it this one?), or what versions of Roxen the bug is
> in.
Roxen developers don't consider it a bug. Hence, they wil not fix it.
Here should be a working patch (this way it gets into the archives, and
is really small anyway ;). cd to your Roxen directory (ie.
/usr/local/roxen and run patch
$ patch -p0 <content-length.patch
Restart, and it should be fine.
--
In flying I have learned that carelessness and overconfidence are
usually far more dangerous than deliberately accepted risks.
-- Wilbur Wright in a letter to his father, September 1900
--------------98581B9F845A5EF32EE19AB2
Content-Type: text/plain; charset=us-ascii;
name="content-length.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="content-length.patch"
--- server/modules/scripting/cgi.pike Wed Jan 26 18:16:53 2000
+++ server/modules/scripting/cgi.pike Wed Jan 12 00:49:06 2000
@@ -487,6 +487,9 @@
result += header+": "+value+"\r\n";
break;
+ case "content-length":
+ break;
+
case "server":
sv_received=1;
result += header+": "+value+"\r\n";
--------------98581B9F845A5EF32EE19AB2--