I am not curtain how it is handled exactly but I do know that it is not a
meta refresh. The page has to go to the user for a meta refresh to work.
The page that a calls a CFLocation never goes to the user (this why cfcookie
and cflocation do not play well together cookie does not get set if a
cflocation is called after the cfcookie). I believe that all the
redirection is handled on the server side. The custom tag CF_location uses
HTTP header calls to do a refresh so cookies do get set and HTTP header
settings are more reliable than meta refresh. Hope this helps. Oh and the
CF_location custom tag can be found on the fusebox site.
Daniel D.
-----Original Message-----
From: Russell K Young [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 13, 2001 9:51 AM
To: Fusebox
Subject: cflocation
Greetings
Does anyone know how the cflocation tag is handled by cold fusion server?
Is <meta http-equiv="Refresh" content="http://www.xyz.com"> involved in
anyway. It has been found that the refresh meta tag severely hampers
performance.
Russell
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
