>> Ah. Gottcha. You are wanting a reverse proxy. > > Darn, sorry, I should have thought about that distinction, like I said, > this is yet another project on my plate so don't have it all down yet :). > >> http://wiki.squid-cache.org/SquidFaq/ReverseProxy >> contains a usable config for accelerating a hidden web server securely. > > Yes, I did come across this but I wasn't sure if this was what I'm looking > for. > In the case of using the proxy, there is a virtual host server on the lan > which handles a dozen or so sites which I wanted to use a reverse proxy to > speed up connections to. > > On the public side, each domain has it's www IP pointing to that virtual > hosting server. The web server is responding based on names so should > squid be pointing to the server or dies it have to know about each site > name as well? > > The examples in the URL seem to show a number of combinations and since > I've not had the chance to actually sit down and start learning this, I > ended up using what I posted, the hole. It's one basic config, with need-based variants. The 'vhost' variation is the one you want by the sounds. Yes the proxy needs to have a list of the domains that are acceptable, just like the virtual host needs to know the domains its serving. A dozen should be easily manageable. If there are too many or need changing frequently they can be moved into a separate file which squid loads into an ACL. If its still just a presentation demo as you said earlier, you can hack a little by configuring the browser used to demo to use the proxy as a normal proxy, but have the proxy itself setup as a reverse. That way the main production DNS stays normal. For a full rollout to go live the domain DNS gets pointed at the proxy instead of the virtual host and things keep flowing. Amos
