[Zope] FastCGI didn't use to need VirtualhostMonster???

[Simon J. Blandford]

I couple of years ago I set up zope using FastCGI & Apache1 and all I
needed in httpd.conf was the following...

FastCgiExternalServer /var/www/html/zope -socket /tmp/zope.soc
-pass-header Authorization

<Location /zope>
SetHandler fastcgi-script
</Location>


When I accessed the default web host e.g. http://localhost/zope I got
zope. No need to set up Virtualhostmonsters or Siteroots in Zope. It just
worked. All the links magically began with http://localhost/zope. That's
why I really liked the FastCGI solution over using proxypass.


Now, I try the same thing with Plone & Apache 2 (which should be the same
in respect of Apache/FastCGI) and all the links just begin with
http://localhost.

Can someone please tell me what changed between then and now. Is it
Apache, FastCGI or Zope? Also, is there anyway I can get this system to
work again without resorting to unsightly Virtualhostmonsters?

Sorry I can't remember the exact versions of applications I was using. I
think Zope 2.4 had just come out and I was using Apache 1.3.x.

Today I am using latest releases with Apache 2.0.x.

Thanks,
SimonB