Re: Strange tux problem

On Mon, Sep 09, 2002 at 03:32:32PM +0200, Alex Kramarov wrote:

> I have noticed that tux exibits the same behaivour with some broken http
> clients if a client provides "\r\n\r\n" instead of the normal "\r\n" in the
> end of the GET request ...

I've researched this further today, and if the request contains
just "\n" instead of "\r\n" after every line (which would be the
case when testing with plain old telnet), tux gives up on
it and forwards it to the backend server.

Another strange thing, that might explain my previous
problems - I'm using the virtual hosting feature, which I believe
strips off any leading 'www.' from the domain. We're using wildcard
hosting on our Apache backend, so whatever you put in front
of domain.com, Apache will serve it. Tux is aware of the domain.com
directory, so requests for static content to www.domain.com and
domain.com will be served by tux without any problems.
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??

Sorry for the many posts yesterday - I was pretty psyched :-)

Cheers,
HC

-- 
Hans Christian Saustrup
Chief of Research/Development
Digital Team ApS - a division of Media-I
Banegaardspladsen 6, 1TH / DK-8000 Aarhus C / Denmark

Value your privacy - use PGP/GPGuard.