Matus UHLAR - fantomas <[EMAIL PROTECTED]> writes:
> > Matus UHLAR - fantomas <[EMAIL PROTECTED]> writes:
> > > I often paste string from clipboard to a mozilla browser, which results
> > > into
> > > tryting to open URL pointed at (it's very good feature of mozilla).
> > >
> > > When this happens, wwwoffle creates directory for the "host", even if it
> > > does not exist. It means that I get many useless directories (with error
> > > messages) created in spool directory.
> > >
> > > Could wwwoffle skip this behaviour, and try to validate hostname (at least
> > > in online mode w/o paren tproxy set up) before creating the directory?
>
> On 01.04.06 16:25, Andrew M. Bishop wrote:
> > If Mozilla is asking WWWOFFLE for a valid hostname then I don't see
> > the problem because WWWOFFLE will fetch the URL that is requested.
> > The directory will be filled with a real web page or an error message.
> >
> > If the problem is that Mozilla is asking for a URL that is not really
> > a URL but a random string then the problem is with Mozilla. Mozilla
> > should be validating the hostname before asking for it.
>
> It's neither the first, nor the second one... It's a string that is valid
> from the DNS point of view, but there is no such record in DNS.
> I understand that if proxy is configured, mozilla does not try to resolve
> the hostname - the DNS might not be working in such cases, so mozilla leaves
> hostname resolution to the proxy.
WWWOFFLE has no way to know if the URL that is asked for is really
wanted or just an accident. This means that it has to try and fetch
the URL even if this fails in the case that you describe.
When DNS fails there can be lots of reasons:
* The DNS server for the domain is down (but the host does exist).
* The name registration has expired (but it did work yesterday)
* The name is being moved to a new DNS server (and will work tomorrow).
* The user typed in a wrong name (the host never has and never will exist).
There are people that will want to know about the first three cases.
They will want to see the error message because it is important to
them to know that the host is not accessible today. The problem is
that there is no way to know that the host does not exist, only that
it is not known by DNS today.
What you are asking for is for WWWOFFLE to behave differently for one
special case (online, no parent proxy) than all other cases. This
will add confusion because error messages will be cached for some
hosts but not other depending exactly when they were requested and the
state of the configuration file.
--
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
