Re: Tux Web Server

----- Original Message -----
From: "Alex Kramarov" <[email protected]>
To: <[email protected]>
Sent: Wednesday, October 16, 2002 2:30 AM
Subject: Re: Tux Web Server


> > TUX (assuming that it doesn't kill the machine every few days) is
> > absolutely perfect for running on its own without the need for Apache
(or
> > any other bloated server) running in the background for this kind of
> > purpose.
>
> with all do respect, you are wrong. Tux is not designed to be a full web
> server, it a web accelerator. the parsing of requests is minimal, and if
tux
> does not understand a request, it will try to forweward it to the backend
> server. if there is no backend server, the client get's an error. as far
as
> i can see in my logs, usually the redirects are caused by some esoteric
> browsers and different download accelerators .

Okay - I retract the suggestion then; I've never taken too much time to
check when normal static content was being passed back to Apache - and
because of keepalive requests sticking with Apache after being handed over
to it, it's hard to tell from Apache's logs which static requests were
passed by TUX due to lack of parsing power.

>From doing considerable manual diagnosis by telnetting in on port 80,
though, I was pretty pleased with TUX's ability to parse and serve suitably
mangled requests (for static content) correctly without resorting to Apache.
YMMV, of course.

M.