I am assuming you mean something like the Client.URLToken or
Session.URLToken? While searching for the aforementioned I stumbled across
the Cfapplication SetDomainCookies attribute. From what I read the
SetDomainCookies attributed places cookies on the host. I suspect there are
advantages/disadvantages to this different approaches. Like maybe some
hosts don't allow cookies, etc.?
Any comments from others?
Anyone aware of a trap and restore cookie tag/snippet
Thanks,
Nick
At 02:06 PM 10/30/2003 -0500, you wrote:
>Nick:
>
>SESSION variables are client-specific. Clients are identified by specifying
>a unique identifier either via cookies or URL parameters.
>
>In order to maintain a session while using multiple CFHTTP requests, you'll
>have to trap any cookies set in one request and specify them in all later
>requests.
>
>--
>Mosh Teitelbaum
>evoch, LLC
>Tel: (301) 942-5378
>Fax: (301) 933-3651
>Email: [EMAIL PROTECTED]
>WWW: http://www.evoch.com/
>
>-----Original Message-----
>From: Nick Baker [mailto:[EMAIL PROTECTED]
>Sent: Thursday, October 30, 2003 1:59 PM
>To: CF-Talk
>Subject: Non-Stick Session Variables?
>
>
>Is there a trick to keeping session variables alive when a Web page is
>called via and CFHTTP, i.e., from another Web site? The session variables
>stick when I called the Web page directly from a browser, but not via
>CFHTTP.
>
>Does this mean the session variables are relying on Cookies? Below is the
>CFAPPLICATION code.
>
><CFAPPLICATION name="TestSite"
> CLIENTMANAGEMENT="Yes"
> SETCLIENTCOOKIES="Yes"
> SESSIONMANAGEMENT="Yes"
> SESSIONTIMEOUT=#CreateTimeSpan(0, 2, 0, 0)#
> APPLICATIONTIMEOUT=#CreateTimeSpan(0, 2, 0, 0)#
> >
>
>Thanks,
>
>Nick
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
