Juraj Variny <[EMAIL PROTECTED]> writes:
> On 29 Aug 2004, Andrew M. Bishop wrote:
>
> > Juraj Variny <[EMAIL PROTECTED]> writes:
> >
> > > On Wednesday 25 August 2004 22:29, Juraj Variny wrote:
> >
> > > > quite often, confirmed request is listed in outgoing, but not fetched
> > > > (neither found in wwwoffle -fetch output). Sometimes even happens that,
> > > > while offline, is the confirmation page shown first, then clicking on
> > > > "confirmation" link reveals the fetched page (instead of expected "Request
> > > > Already Recorded" page).
> >
> > > Sorry, I had full /var/ partition. It is ridiculous that no one program
> > > (except syslog) gave clear diagnostic for such a failure. Everything just
> > > went haywire....
> >
> > There are lots of places in WWWOFFLE where an error message that may
> > be due to a full disk are reported as such.
> The misbehavior cotinues even with plenty of space on the
> partition...problem is apparently rooted somewhere else.
If the request is placed into the outgoing directory then the only way
that it can be removed is if it is fetched. When a file is fetched it
should always report this in the output of 'wwwoffle -fetch'. (There
are currently two cases where this doesn't happen; pages that are in
DontGet and requests that cannot be parsed. I have added messages for
these now.)
I can't see any way how a request can be in outgoing but not be
mentioned in the output of 'wwwoffle -fetch'. It is possible that it
does not appear in the WWWOFFLE lasttime index if the page had not
changed and it wasn't downloaded.
The behaviour when offline with the confirmation page coming up and
then when confirmed the real page coming up is due to the browser. It
is showing you the cached confirmation page instead of asking WWWOFFLE
for a new page.
--
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
