On Fri, 8 Oct 1999, Leslie Mikesell wrote:
> Date: Fri, 8 Oct 1999 16:22:58 -0500 (CDT)
> From: Leslie Mikesell <[EMAIL PROTECTED]>
> To: Stas Bekman <[EMAIL PROTECTED]>
> Cc: Oleg Bartunov <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: 2 servers setup: mod_proxy cacheing
>
> According to Stas Bekman:
> > > I have 2 servers setup and would like to configure
> > > frontend to cache output from backend using mod_proxy.
> > > I tried to add various headers but never seen any files
> > > in proxy directory. I didn't find any recommendation in your
> > > guide how to configure servers to get Apache cacheing works.
> >
> > A good question... Any of the mod_proxy users care to give Oleg (and the
> > guide :) a hand here? I use squid as a front end, that's why I don't have
> > any examples from mod_proxy...
>
> I tried it several versions of apache ago and never got it to
> cache anything as a reverse proxy, but with the same setup I
> could configure a browser to use the box as a normal proxy and
> it would cache those pages. I used squid for a while, then
> switched to an apache that serves the images and static pages
> directly and proxies everything else to mod_perl (using mod_rewrite
> to decide).
Hmm, very interesting solution but I can't explain every user
please configure your browser in special way to browse my site.
I'd prefer to get apache's mod_proxy cacheing mechanism to work
as supposed. It's very mysterious part of apache code
Who's the author of mod_proxy ? May be he will be able to
show us some working example. Also I found one very interesting
posting by Andreas concerning http headers and caching
but lost URL. I remember it had to be a part of Guide.
What's the status of this chapter ? Is it possible to find
it in Web ? We really need working example to play with.
The problem becomes more complex if we'll take into account
not only proxy cacheing feature but also clients browser
cache. I'd prefer to have control on both of them,
for example proxy-frontend caches output from cgi-backend and
browser also could cache documents, so user could
go back and forward without contacting even with proxy.
Moreover, user could also use proxy server and this
proxy will contact with proxy-frontend. What's the mess :-(
I use Mason on cgi-backend to produce dynamic output
(semantically static using Andreas terminology)
which also has some internal cache. Fortunately
it's fully controlled without any headers :-)
I'd prefer to stay with HTTP 1.0 because most proxies
doesn't support 1.1 yet (btw, what's about apache proxy)
Regards,
Oleg
>
> Les Mikesell
> [EMAIL PROTECTED]
>
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
