I'd hate to have to find all the cookie reads in all applications and have to pair them with cookie-drops to keep the things in place.
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
