> Date: Mon, 13 Jun 2005 10:27:07 -0400
> From: Paul Winkler <[EMAIL PROTECTED]>
> Subject: Re: [Zope] ACTUAL_URL vs. VIRTUAL_URL
> On Mon, Jun 13, 2005 at 02:37:44PM +0200, Bert Vanderbauwhede wrote:
> >
> > What's the difference between ACTUAL_URL and VIRTUAL_URL in the REQUEST 
> > object?
> VIRTUAL_URL only appears in the REQUEST when VirtualHostMonster does its
> thing. So if you are not using virtual-hosting, VIRTUAL_URL does not
> appear in the request. This is inconvenient; we wanted something
> that would always be available and would always mean
> "the URL originally sent by the client".  This is what ACTUAL_URL is.

OK, thank you. So ACTUAL_URL is safe to use in all cases.

> Having said that, I'm not clear on the difference between
> ACTUAL_URL and URL :-)

<drzoidberg>Hurray! I'm useful!</drzoidberg>

I think I can answer that one.

I have created a product to redirect authenticated users to HTTPS,
using a pre-traversal hook. In the hook, it turned out that URL is the
url to the folder with the pre-traversal hook, and not the requested
url. I think that URL is modified during the traversal process, so
that it contains the url for the current object. Only when the last
object is reached does URL contain the full requested url, and is it
equal to ACTUAL_URL.

Zope maillist  -  Zope@zope.org
**   No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to