Re: Re: confused reloading of pages (bad config)

mi <[email protected]> writes:

> amb-Uxr6IM1mbv2TY6FTCsQk+9Bc4/[email protected] (Andrew M. Bishop):
> > Actually it could be the confirm-requests option that does this.  If
> > you load any other page and force a refresh (press control-refresh) in
> > the browser (or shift-refresh or however your browser forces a
> > refresh) does it show a "confirm request" page?
> With the buggy setting, no. confirm-request only appears when offline.
> When online, ctrl-r reloads a page immediately.
> 
> See attached debug log *confirm-yes*

When you make the forced request when offline the first time you get
an internal WWWOFFLE page that asks you to confirm the request.  None
of the other images and stylesheets that are normally in this page are
requested at all.

The second time that you do the forced refresh when offline the
original page is visible again.  I don't know why the result is
different the second time that you force the refresh, you should still
see the confirmation page.  It could be something to do with the
headers that the first page sent back compared to the headers that the
internal page sent back.  Anyway this time the stylesheets and other
URLs in the page are visible to the browser so it does a forced
refresh on them.  This means that they are not visible because you get
the confirmation page for each of them (although it is not visible).

The next time you force the refresh you get the confirmation page
again.

The next time you force the refresh you get the original page and the
images in it are OK.  This is because they were forced last time so
they are also going on a two step cycle.

The next time is the same as the first time.


So it looks like this (and repeats)

1) normal images -> confirmation page
   no images requested

2) confirmation page -> normal page
   images -> confirmation page for images

3) normal page -> confirmation page
   no images requested

4) confirmation page -> normal page
   confirmation page for images -> normal images



> How can i get the 'confirm-reuest = yes' feature without problems ?

I don't know.  I can reproduce it here with confirm-requests=yes.

If you want to refresh the page you need to confirm it, if you don't
want it then don't confirm it and don't press refresh again.


> > > LocalHost
> > > {
> > > woody
> > > localhost
> > > Localhost
> > > 127.0.0.1
> > > woody.lan0
> > > 192.168.0.1
> > > 
> > > ::ffff:127.0.0.1
> > > ip6-localhost
> > > ::1
> > > }
> 
> > If your computer responds to the hostname 'woody' or 'woody.lan0' and
> > has IP address 192.168.0.1 then there is no problem
> Yes, that is the case.
> 
> As i see it, 127.0.01 and 192.168.0.1 are logically two different NICs (or machines).
> I always got confused thinking of {woody, 127.0.0.1} on the one hand and
> {woody.lan0, 192.168.0.1} on the other.
> Does it not matter which one i tell wwwoffle is 'localhost' ?

The first listed one must be one that is accessible on the network
from all hosts.  So if you have any other hosts that access the
computer then using localhost is no good.  The way that you have got
it configured seems OK.  If it works from the hosts in 192.168.0.*
then it is OK.

-- 
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop                             amb-Uxr6IM1mbv2TY6FTCsQk+9Bc4/[email protected]
                                      http://www.gedanken.demon.co.uk/

WWWOFFLE users page:
        http://www.gedanken.demon.co.uk/wwwoffle/version-2.8/user.html