Re: Strange tux problem

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On September 10, 2002 09:14 am, Hans Christian Saustrup wrote:
> On Tue, Sep 10, 2002 at 08:18:42AM -0400, Hans Christian Saustrup wrote:
> > Here comes the funny part - if I request something from
> > foo.domain.com, I suppose tux would be looking for a directory
> > called foo.domain.com, fails to locate this and..  closes the
> > connection?!? As I understood, tux should forward any requests it
> > can't serve to the backend??
>
> Confirmed - if I create an empty directory foo.domain.com, tux will give
> up and forward the request to Apache, instead of just closing the
> connection. Since the usual response from tux when it's confused is
> something like "page not found", I suspect closing the connection
> without any response is a bug? :-)

I agree, and I'm relying on the current behavior. Some clients refuse to send 
the fqdn and use the IP address in the URL. Tux doesn't understand that the 
IP address corresponds to www.foo.com. One way to make this work is to create 
an empty directory with the IP address as the directory name. Tux then 
forwards the request on to Apache. (One such client is from 
themindelectric.com (GLUE)). I've asked them to consider sending the fqdn but 
they will not so tux needs to support this behavior.

> Cheers,
> HC

- -- 
The level of productivity in an ecosystem is directly
proportional to its diversity.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9fgQHBtoFHHwdJ/cRAoIKAJ9CXkaVEnhTShcsEx/41Rwm03Kx5gCfSeEG
15FV3Bx3X/MDytJH3PPfb3A=
=Z6As
-----END PGP SIGNATURE-----