Robert Shubert at Tronics verified the existence of this bug. His server is running on Windows 2000. If you read a cookie, it destroys the cookie. The file for the cookie disappears. This is when using IE.
The workaround of reassigning the cookie after reading it is still a problem for me. My cookies were set up to expire in 30 days. If I continually reassign the cookie after reading it, then it will become a perpetual cookie that never expires.
With Enterprise: When will this bug be fixed? This is a real problem for those of us that make use of cookies.
Stefan
At 07:42 AM 8/27/2003 -0700, you wrote:
This bug is causing me some difficulty, I have to remember to re-write the cookie every time I read it so that it won't become a session cookie.
This is MacOS X version application server.
On Wednesday, August 27, 2003, at 07:21 AM, Stefan Gonick wrote:
Could With Enterprise please confirm or deny the existence of this bug?
I run affiliate programs that are based on cookies. I recently moved from T2000 to W5 version 062, and I have noticed a reduction in the conversion rates of my affiliates. This could be due to the cookie bug mentioned. If so, this is very serious for me! I really need an answer to my question.
Thanks, Stefan
At 01:05 PM 8/25/2003 -0700, you wrote:Oh, by the way, that's not what I observed. I set a cookie with the assign action, close the browser, open it up again, check cookies, and find it's there with the right expiration date. It is the simple reading of the cookie, e.g., a line line taf:
@@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
========================================================
Database WebWorks: Dynamic web sites through database integration
http://www.DatabaseWebWorks.com
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
