Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Cookie clearing problem
Wed, Feb 5 2014 6:12 PMPermanent Link

aberas

This code:

if Cookies.Exists('namehere') then
 Cookies.clear('namehere');

woks on Firefox, but neither in Chrome nor in Safari the cookie is emptied.

Any help?
Thu, Feb 6 2014 6:41 AMPermanent Link

aberas

I've narrowed it down a little more:

the cookies I'm checking are created not from the directory where the EWB app runs ( / ) but from another ( /images ), where I keep several HTMLs which are displayed in a TPage. When I click them, they create a cookie.

Firefox manages them as if they are from the same source, and clear them without a problem.
Chrome reads them, but is unable to clear them.
Thu, Feb 6 2014 7:42 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com


<< I've narrowed it down a little more:

the cookies I'm checking are created not from the directory where the EWB
app runs ( / ) but from another ( /images ), where I keep several HTMLs
which are displayed in a TPage. When I click them, they create a cookie.

Firefox manages them as if they are from the same source, and clear them
without a problem. Chrome reads them, but is unable to clear them.  >>

Yeah, this falls under "security", which is where the majority of disparate
behaviors exist in the browsers.  This is primarily because they all have
various settings that can modify how they behave.

In general, though, I would *always* make sure that the path being used for
manipulating a specific cookie is *exactly* the same as the path used when
the cookie was created.

Tim Young
Elevate Software
www.elevatesoft.com

Thu, Feb 6 2014 8:56 AMPermanent Link

aberas

"Tim Young [Elevate Software]" wrote:


<< I've narrowed it down a little more:

the cookies I'm checking are created not from the directory where the EWB
app runs ( / ) but from another ( /images ), where I keep several HTMLs
which are displayed in a TPage. When I click them, they create a cookie.

Firefox manages them as if they are from the same source, and clear them
without a problem. Chrome reads them, but is unable to clear them.  >>

Yeah, this falls under "security", which is where the majority of disparate
behaviors exist in the browsers.  This is primarily because they all have
various settings that can modify how they behave.

In general, though, I would *always* make sure that the path being used for
manipulating a specific cookie is *exactly* the same as the path used when
the cookie was created.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks, Tim. I was getting crazy trying to narrow it down to something explainable.
Will see another way to deal with this.


Image