Paul Slootman <[EMAIL PROTECTED]> writes:
> A bug reported on the debian package. He's got a point:
>
> On Thu 14 Mar 2002, Thorsten Gunkel wrote:
>
> > Package: wwwoffle
> > Version: 2.7-1
> >
> > | $ export http_proxy="http://localhost:8080/";
> > | $ wget www.debian.org
> > | --10:24:00-- http://www.debian.org:80/
> > | => `index.html.1'
> > | Connecting to localhost:8080... connected!
> > | Proxy request sent, awaiting response... 200 OK
> > | Length: unspecified [text/html]
> > ^^^^^^^^^^^^^^^^^^^
> > |
> > | 0K -> .......... ....
> > |
> > | 10:24:03 (5.09 KB/s) - `index.html.1' saved [14535]
> >
> > But afterwards:
> >
> > | $ wget www.debian.org
> > | --10:24:13-- http://www.debian.org:80/
> > | => `index.html.2'
> > | Connecting to localhost:8080... connected!
> > | Proxy request sent, awaiting response... 200 OK
> > | Length: 14,535 [text/html]
> > ^^^^^^^^^^^^^^
>
> I've verified that wwwoffle doesn't report the length if the object's
> not in the cache; first time it's not in the cache, second time it is.
> This is unexpected, I'd say. Of course the Length header is not a
> compulsory header, but it's useful to see whether the object you're
> trying to download is 100k or 10000k.
This is (should be) fixed in version 2.7a of WWWOFFLE. It was due to
the quick-fix that I applied in version 2.6d that stopped the
truncation of pages when the request-compressed-data option was used.
The fix at that time was to remove the Content-Length header from all
pages visited when online if zlib was compiled in. The more
considered fix is to only remove the Content-Length header when
compression is being used by WWWOFFLE as a result of the
request-compressed-data or reply-compressed-data options.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.7/user.html
