George Lee wrote:
http://my.domain.org/VirtualHostBase/http/my.domain.org:80/contentPages
which does not work. Plone folks suspected this was a Zope problem.
Oh really? ;-)
When Plone sets the came_from, it draws on the REQUEST variable. It
first looks to see if there is a VIRTUAL_URL in
Two main questions:
(1) Does anybody *have* good documentation on VIRTUAL_URL and how it
interacts with CookieCrumbler and VirtualHostMonster?
(2) Does anyone know how to debug VirtualHostMonster or other Python
libraries while running a Zope instance (it lives in Python not in
Zope, so I
(2) Does anyone know how to debug VirtualHostMonster or other Python
libraries while running a Zope instance (it lives in Python not in
Zope, so I don't know if I change the code there if those changes will
actually get executed)?
Oh wait it is in a Zope product, scratch that.
Peace,
George Lee wrote:
On my Plone site, in CookieCrumbler.py, VIRTUAL_URL is not found in
the request variable even though I have a Virtual Host Monster. This
means that when logging in, the came_from URL that my site directs
to becomes something ugly like
What version of Zope are you using?
Why
Zope 2.8.1
In Plone 2.1.1, when I try to access a page Anonymous does not have
permission to see, it redirects to a login. While doing so, it sets a
came_from variable with the URL I'm trying to access. It sets an ugly
http://my.domain.org/VirtualHostBase/http/my.domain.org:80/contentPages
Hi,
On my Plone site, in CookieCrumbler.py, VIRTUAL_URL is not found in
the request variable even though I have a Virtual Host Monster. This
means that when logging in, the came_from URL that my site directs
to becomes something ugly like
