It uses two CFHEADER tags to pass a 302 HTTP response back to the client so
that cookies will get set, which CFLOCATION doesn't do.  It might also allow
for you to select between server and client side redirects, but I don't
know.

something like this:

------------------------------------------------------------------------
<cfparam name="attributes.addtoken" default="false" />
<cfif attributes.addtoken>
   <cfset attributes.url = attributes.url & "&cfid=#cfid#&cftoken=#cftoken#"
/>
</cfif>

<cfheader statuscode="302" statustext="object temporarily moved" />
<cfheader name="location" url="#attributes.url#" />
<cfabort />
------------------------------------------------------------------------

---
Barney Boisvert, Senior Development Engineer
AudienceCentral
[EMAIL PROTECTED]
voice : 360.756.8080 x12
fax   : 360.647.5351

www.audiencecentral.com


> -----Original Message-----
> From: Sean A Corfield [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 03, 2003 3:41 PM
> To: CF-Talk
> Subject: Re: <cf_location> custom tag and CFMX (not working)
>
>
> On Thursday, Jul 3, 2003, at 08:24 US/Pacific, Jamie Jackson wrote:
> > It appears that CF_Location v2.0.1, V1.0 (Jordan Clark). Doesn't work
> > under CFMX. I could hack it to get it working, but if anyone has the
> > fixes at their fingertips, would you let me know?
>
> Just out of curiosity, what does cf_location provide that the built-in
> cflocation does not?
>
> Sean A Corfield -- http://www.corfield.org/blog/
>
> "If you're not annoying somebody, you're not really alive."
> -- Margaret Atwood
>
> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq

Get the mailserver that powers this list at 
http://www.coolfusion.com

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to