Re: [squid-users] Squid as an HTTP accelerator (fwd)

For this perverted way of supporting virtual servers you will still need
a redirector (the URL-path needs to be rewriten).

If you can make the Zope server understand normal domainbased virtual
servers no redirector is required. Simply set up the server as if it was
the server for the domains.

--
Henrik Nordstrom
Squid Hacker
sean.upton@uniontrib.com wrote:
> 
> I'm just curious to find out what extent rproxy can rewrite URLs without a
> redirector...
> 
> The application server that I primarily use (Zope, which has a built-in http
> server) supports virtual-hosting in a somewhat different way, using
> something called a VirtualHostMonster, requiring the path be modified to in
> order to have the app server dynamically rewrite environment variables used
> to build hyperlinks on pages with the externally-visible URLs.  In this
> situation, a redirector is still going to be required, if I understand
> correctly?  Or would Squid-rproxy be able to rewrite a URL like below?
> 
> An example of my rewrite rules (from pyredir, the redirector I use):
> ^http://classifieds.signonsandiego.com[/]?(.*)
> =http://nodes.foo.com:9673/myhost/VirtualHostBase/http/myhost.foo.com:80/myh
> ost/VirtualHostRoot/\1
> 
> In this scenario, Zope runs on port 9673; queries to this get the URLs used
> in writing output content as http://myhost.foo.com/ as a base, using the
> /myhost folder as a content root.
> 
> Sean