Re: Setting up LocalHost and LocalNet SOLVED (sort of)

Micha <[email protected]> writes:

> Ok, tracking on. I just log here what i try.
> 
> I made it the legacy way: /etc/hosts now has,
> 
> 127.0.0.1       localhost		
> 192.168.1.2	woody.lan1	woody     # eth0
> 
> What irritates me is, wwwoffle still says, 'transferring data 
> from localhost' it's no more 'localhost' isn't it ?

You haven't said what you are doing to get this message.  If you have
got 'localhost' or '127.0.0.1' set as your proxy or are visiting the
URL 'http://localhost:8080/' or 'http://127.0.0.1:8080/' then this
message would be correct.

> And still the browser hangs.

> short overview of the environment:
> 
> wwwoffle.conf now has 'woody' as first LocalHost entry.
>  'localhost' is the second entry there (is it necessary at all ?).
> There is a "*.lan1" entry in LocalNet, and also in AllowConnectHosts.

You should put in all of the names of the computer so that WWWOFFLE
will not act as a proxy for them but redirect to the first named one.

> bind-ipv4 is '0.0.0.0' which means the first entry of LocalHost will be
> used by wwwoffle, as socket, AIR ?

No, it means that all interfaces on the computer will bind the socket
(so that 127.0.0.1 and 192.168.1.2 will accept connections).

> I looked over the browser settings, and noted gthat aleon just calls
> 'gnome-network-preferences' (i don't start any gnome-session since
> long) and there were 'except from proxying' entries for this host, they 
> are years old, today i  think they are not really clever: 
> 127.0.0.1, 
> localhost, 
> woody,
> woody.lan1. 
> I guess the first 2 are not necessary at all ? - i just deleted them.
> But this shouldn't have any direct impact, AFAICS, cause it 
> worked for some years, flawless.

You should not need any of these.


> The browser now hangs several minutes minutes even when loading
> wwwoffle pages, like the http index. But this is weird, now nothing 
> works at all, not even calling http://192.168.1.2:8080...
> galeon always replies:  "localhost" is not responding.
> Ooops, can't even load a page from the net anymore ('not
> responding'). Typical netfilter feature.... checking the iptables: 

[snip: problem found with iptables]

At least you have found your problem now.


> ps. Oops - but what does this mean? Requesting
> http://127.0.0.1:8080/index.html  -->
> 
> WWWOFFLE File Locked
> Your request for URL http://127.0.0.1:8080/index.html
> is already being modified by another WWWOFFLE server. 
> 
> This address now even appears in the http index! 
> http://127.0.0.1:8080 No Pages

See my comment about adding localhost and 127.0.0.1 to the LocalHost
section of the config file.

> Hmmm...127.0.0.1 is in LocalHost ...no ? 
> There's 'localhost' in that list, but not 127.0.0.1.
> sigh. 
> You see this isn't that easy to understand.

You need to add all of them because WWWOFFLE does not do a reverse
lookup.

-- 
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.9/user.html