> 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.

Those things allow you to manage session tokens for your users' browsers,
and don't affect your use of CFHTTP to talk to another server. If you're
using CFHTTP, your CF code IS the browser, and will be responsible for
reading cookies set by the remote server, and for returning those cookies on
subsequent requests. You can see these cookies by looking in either
CFHTTP.Header or CFHTTP.ResponseHeader, and you can set these cookies on
subsequent requests using CFHTTPPARAM.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444

[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to