apache sends bad content length

To: current-users%NetBSD.org@localhost
Subject: apache sends bad content length
From: Thilo Jeremias <thilo%nispuk.com@localhost>
Date: Mon, 15 Jun 2009 00:30:21 +1000

Hello there,

Anyone know how to fix this:

I use NetBSD current and  apache 2.2.11
apache now returns a content length of .... 0x2bffffffd5 .... (well
really big )

(of course actually trying to transmit a file causes apache to use 2gb
of mem and gets the system swappin.....)
thanks for the help


$ curl -v  http://rescue
* About to connect() to rescue port 80 (#0)
*   Trying 192.168.0.41... connected
* Connected to rescue (192.168.0.41) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.16.3 (i686-pc-cygwin) libcurl/7.16.3 OpenSSL/0.9.8k
zlib/1.2.3 libssh2/0.15-CVS
> Host: rescue
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Sun, 14 Jun 2009 14:15:20 GMT
< Server: Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.9-dev DAV/2
< Last-Modified: Sun, 14 Jun 2009 14:15:20 GMT
< ETag: W/"3860e-2c00000001-59cdde3400046c49"
< Accept-Ranges: bytes
< Content-Length: 188978561025
< Content-Type: text/html
<
* transfer closed with 188978560981 bytes remaining to read
* Closing connection #0
curl: (18) transfer closed with 188978560981 bytes remaining to read
<html><body><h1>It works!</h1></body></html>

Prev by Date: daily CVS update output
Next by Date: OpenSSH in current - bad packet length
Previous by Thread: ipmi(4) sensor driver update
Next by Thread: Proposed changes to acpi_tz sensor behavior
Indexes:

Home | Main Index | Thread Index | Old Index