Hi, What's the difference between ACTUAL_URL and VIRTUAL_URL in the REQUEST object? Bert...
On Mon, Jun 13, 2005 at 02:37:44PM +0200, Bert Vanderbauwhede wrote:
Hi,
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. Having said that, I'm not clear on the difference between ACTUAL_URL and URL :-) -- Paul Winkler http://www.slinkp.com
Paul Winkler wrote at 2005-6-13 10:27 -0400:
... Having said that, I'm not clear on the difference between ACTUAL_URL and URL :-)
"URL" is in fact computed. Thus, it can be both shorter (e.g. in case of a PythonScript with active "traverse_subpath"), longer (e.g. in case of ":{method|action}" request variables) or almost unrelated (e.g. in case of active '__before_traverse__' hooks (such as VHM)). -- Dieter
On Mon, Jun 13, 2005 at 07:15:45PM +0200, Dieter Maurer wrote:
Paul Winkler wrote at 2005-6-13 10:27 -0400:
... Having said that, I'm not clear on the difference between ACTUAL_URL and URL :-)
"URL" is in fact computed.
Thus, it can be both shorter (e.g. in case of a PythonScript with active "traverse_subpath"), longer (e.g. in case of ":{method|action}" request variables) or almost unrelated (e.g. in case of active '__before_traverse__' hooks (such as VHM)).
Ahh, right, thanks, I had forgotten traversal hooks that were mentioned in the original discussion about this. So, all told, ACTUAL_URL is quite valuable: AFAICT it is the only value that is guaranteed to represent the "actual" URL seen by the user, and it is always available. -- Paul Winkler http://www.slinkp.com
participants (3)
-
Bert Vanderbauwhede -
Dieter Maurer -
Paul Winkler