Dan Jacobson <[EMAIL PROTECTED]> writes:
> >> but no mention of if the server closes the connection...
>
> A> If the server closes the connection then it is the end of the file.
>
> also perhaps: server severs connection before Content-Length is
> reached; we hangup vs. server closing connection ... ok never mind.
There is a difference between when the server actively closes the
connection on us and when we cannot read any more data. The
assumption in WWWOFFLE is that an active close of the connection is
the end of the data even if we didn't get the specified number of
bytes.
> [ramble:] Anyways, I assume timeout-download-keep is the one that will
> save partially downloaded files when it is we that hang up the
> phone... I suppose "server connection times out" is what happens when
> we hang up...
Yes, when the connection is not actively closed by the server but
there is no more data coming in the timeout period this is the option
that is used.
> ok I will try timeout-download-keep... I was just hoping
> ... yes ... perhaps in the addcacheinfo box, a note could be added
> that this file is incomplete... hmmm, probably the only record of
> that would be in the logs... I'm just thinking, now that I will allow
> partial files, I was wishing that any time I visit that file offline,
> I could be reminded that it is incomplete... hmm, a box at the top of
> the file...
The error code for the page will be changed to 503 in the cache so
that next time the page is visited when online or with wwwoffle -fetch
it will be re-fetched.
If you are worried about having incomplete files in the cache then
don't enable this option. If you are viewing the page when online the
browser will show the incomplete page anyway even if the cached
version is changed to an error message.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.8/user.html
