AW: Tux / apache / squid(?) questions

[Max Helmet]

Hi,

TUX accellerates HTTP by serving static HTML and image files without the
overhead of an  user/kernel switch and by reducing the request processing to
an absolute minimum. It just "peeks" into the incoming request and then
decides whether it can serve the response by itself or better leave it as is
and hand the job over to the user-space web server. After the hand-over TUX
stops dealing with the request, leaving sole responsibility to the web
server of choice. In this process, no proxying and no HTTP redirection is
involved.

This said, TUX will not cache any responses coming from the user-space web
server. TUX specializes in serving static files and does extremely well at
it - nothing more, nothing less.

If your primary concern is reverse proxying, TUX probably isn't right for
you.

Regards,
Max

> Just another question (if I may):
>
> If tux calls apache in the same machine (apache1) and this apache redirect
> the request to an apache web server in another machine (apache2), the
> answer will be:
>
> 1.
> apache2 --> apache1 --> tux --> client
> (Does TUX cache apache2 answer?)
>
> OR
>
> 2. apache2 --> apache1 --> client   (NO TUX and no tux caching)
>
> Regards,
> lisbon_pt
>
>
>
> On 2/24/06, Max Helmet <max at expires-2004.workforce.de> wrote:
> > Hi,
> >
> > TUX can only call the other web server on the same server, it
> has no ability
> > yet to forward or proxy requests to a separate server.
> Therefore you will
> > have to go for the 2nd solution: Browser --> TUX -> Squid --> IIS.
> >
> > In addition to that, you could mirror the IIS site via httrack
> to the TUX
> > frontend servers and create cron jobs that regularly update the
> local copy.
> > This way you could fully leverage the accelleration capabilities of TUX.
> >
> > Regards,
> > Max
> >
> > > I have a TUX (?) problem, but I would like to share with this
> community.
> > >
> > > browser /cache ----connect---> FRONT END --- possible
> redirect to BACKENDs
> > >                                                          (1)
> > >                    (2)
> > >
> > > In (1), I have TUX and apache 1.3 with same DOCROOT
> > > so I guess TUX will really accelerate responses for request which
> > > objects are in this DOCROOT.
> > >
> > > however if objectas are not in (1), there will be redirected
> to (several)
> > > backends (IIS 5.0 - with header expires configured for 9 days).
> > >
> > > My doubts are (if someone could help - hope I'm not demanding
> too much):
> > >
> > > 1. would the answers sent from (2) throught (1) be cached by TUX?
> > >     (TUX doesn't seem to me a cache, but an accelerator for user-space
> > >      web-server, as apache)
> > >
> > > 2. The solution could be:
> > >     1. have squid as cache in FRONTEND
> > >     2. requests not served by TUX should be redirected to squid
> > >     3. squid would contact BACKENDs (redirect) and will cache answers
> > >         from backend
> > >
> > > I really would appreciate any help (I know you all have to do but
> > > maybe already
> > > faced same quesions)
> > >
> > > kind regards,
> > > lisbon_pt
> > >
> > > _______________________________________________
> > > tux-list mailing list
> > > tux-list at redhat.com
> > > https://www.redhat.com/mailman/listinfo/tux-list
> > >
> >
> > _______________________________________________
> > tux-list mailing list
> > tux-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/tux-list
> >
>
> _______________________________________________
> tux-list mailing list
> tux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/tux-list
>