You have that ahead of your CFAPPLICATION tag?  Definitely won't work
if it executes afterwards, but I have no idea if it'll work before.

A better route would be to check and see if a user has cookie support,
and if they do, don't set the URL variables anywhere.

cheers,
barneyb

On Mon, 30 Aug 2004 14:49:00 -0700, Nathan Strutz <[EMAIL PROTECTED]> wrote:
> I've got an app where we put the urltoken in all the links on the site,
> including cflocations and everything for those ~2% who don't surf with
> cookies.
>
> Sometimes, due to bad proxy servers, and even with no-cache http
> headers, pages get cached and a user may enter another user's session
> when clicking on a link with someone else's cfid and cftoken.
>
> I'd like it to prefer the cookie over the URL variables for cfid, and
> cftoken, but it won't do that.
>
> Here's the code I tried putting before my <cfapplication> tag:
>
> if (isDefined("cookie.CFID") and isDefined("cookie.CFTOKEN") and
> isDefined("url.CFID") and isDefined("url.CFTOKEN") and cookie.CFID neq
> url.CFID and cookie.CFTOKEN neq url.CFTOKEN) {
>   url.CFID = cookie.CFID;
>   url.CFTOKEN = cookie.CFTOKEN;
> }
>
> summed up: if everything exists but they don't match, use the cookie
> instead of the url vars.
>
> This doesn't work. CFMX still prefers the URL vars over cookies. Does
> anybody know what I can do to fix this?
>
> thanks,
>
> -nathan strutz
> http://www.dopefly.com/
--
Barney Boisvert
[EMAIL PROTECTED]
360.319.6145
http://www.barneyb.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to