On Jan 6, 2009, at 1:18 AM, Sebastian.Lux wrote:
I read this article twice and understood most of the RewriteRule you
posted,
anyway it does not work.
I think this is due to the [zope_path] which might be wrong in my
RewriteRule.
By the way just to make it clear: I do not need to do anything with
the VHM
in the zope db itself (e.g. adding mappings). Just having a standard
VHM in
the root of zope is enough.
Here is my RewriteRule:
RewriteRule ^/myPortal($|.*)
http://Server2:8000/VirtualHostBase/http/Server1:80/Plone/
VirtualHostRoot/_vh_myPortal$1
[L,P]
Assuming the zope path is correct, this looks okay. The zope path is
just the path to the Plone directory from the Zope root. Do you know
how to get to the Zope root?
If you're still having problems, I'm guessing either the zope path is
incorrect or you have an access rule or siteroot interfering with the
VirtualHostMonster magic. I don't recall if you said what OS your
Zope installation is on, but a common (and annoying) problem with
Windows installations is the default access rule that you get
sometimes with a Windows installation. Perhaps you have two ports
available on your instance? By default, I think there is usually a
Port 80 for Plone root access (which is the access rule at work) and
Port 8080 for the regular Zope root access (sometimes called the
management port). Maybe try the other port, or delete the site root?
http://plone.org/documentation/faq/accessrule
Ric
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
