Andrew M. Bishop
Sun, 13 Oct 2002 00:36:02 -0700
Jan Tisje <[EMAIL PROTECTED]> writes:
> I would call it a windows problem... but I have it since upgrading
> form 2.7d to 2.7f:
>
> opera 6.05 and ie55 use the dialup IP adress to connect to the
> control part of wwwoffle. this IP changes and is
> therefore not allowed to connect to wwwoffle.
The browsers should not be accessing the control port at all.
> they can both access the proxy functions, but when trying to fetch
> or set wwwoffle to online, while the computer is online, I only
> get the HTML page that says:
>
> "This page is equivalent to using wwwoffle on the command line
> wwwoffle $command -c wwwoffle.conf
> The output of this command is: "
>
> and the output is empty.
>
> I do not get an error message like "access denied".
> but wwwoffle logs that it did not allow access from dialup ip.
This is not what I would expect from the code. If the socket cannot
be opened then an error is returned. But there is a difference, the
socket can be opened, but then it is closed again by the server. I
have updated the code to return an error message in this case.
What do you have as the first entry in the LocalHost section of the
configuration file? You should have 127.0.0.1 or some other fixed IP
address rather than a name. This is the IP address that WWWOFFLE will
try to contact to send the command and that seems to be failing for
you.
> Perhaps the inter process communication between some wwwoffle
> threads/processes does not work?
It does not use inter process communication, it uses a socket the same
way as if you used the command line.
--
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