@@cookie$mycookie
that causes it to be overwritten by a session cookie. I set MSIE to alert me when a cookie is being written, and sure enough, when I run the line-line taf, I get the alert saying "do you accept a cookie that expires at the end of this session?"
Can't imagine this to be a dev studio problem, given that one simple tag tripped the overwriting of the cookie.
On Monday, August 25, 2003, at 12:37 PM, Bill Conlon wrote:
There is a bug.
If you set a cookie using the ASSIGN ACTION, the cookie will expire immediately, no matter what date you set.
Instead, set the cookie with the <@ASSIGN> metatag.
I set a cookie with an expiration some time in the future, 180 days.
I read the cookie and it turns into a session cookie. I look all through my code to see where I might have done this. I do a simple experiment and set a cookie with one taf with one line. I check it to make sure that the expiration is the proper date in the future.
I set the browser to prompt me for each cookie.
I read that cookie with another one line taf, and up pops the alert,
asking me if I want to set the cookie, which expires at the end of this
session.
Is it normal for cookies to get overwritten by session cookies on a reading?
______________________________________________________________________ __
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
Bill Conlon
To the Point 345 California Avenue Suite 2 Palo Alto, CA 94306
office: 650.327.2175 fax: 650.329.8335 mobile: 650.906.9929 e-mail: mailto:[EMAIL PROTECTED] web: http://www.tothept.com
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
