Re: Cookies
by "Darrell King" <darrell(at)webctr.com>
|
Date: |
Tue, 20 Feb 2001 07:31:32 -0500 |
To: |
<hwg-techniques(at)hwg.org> |
References: |
p |
|
todo: View
Thread,
Original
|
|
Is he staying under the same domain? Leaving the domain leaves
the cookie behind to, so to speak. This can be a problem in
environments where a shared security certificate is used for the
secure connections, as that cert is usually in a different domain
from the rest of the site...
D
----- Original Message -----
From: "Sunil Bahl" <sunilbahl(at)tigersden.i-p.com>
Dear Friends,
I have a friend who is pulling his hair out trying to get some
cookies to work on his site.
The cookie is supposed to save the image ids of those pictures the
user wants to buy. So basically a shopping cart. However unlike
many shopping cart models, all the products are not all neatly
listed
on one page. Every image page in the online galleries should have
an "order" button that saves the image id to the cookie. When the
person goes to the checkout my friend wants to be able to read the
cookie, make a
table of the image ids to be confirmed and then process it. He can
currently browse a directory of images, adding or deleting them
from the cookie
but when he goes to the checkout page, the cookie is empty. Now he
knows that there is a path issue here. You can only access the
cookie in the directory and subdirectories where it was created.
To deal with this, he used the "path" attribute set to the root
("path=/") but it doesn't seem to work. Any ideas?
If he goes back from the checkout page to the galleries and add
another image to the basket then it comes up as if they're now two
cookies. It's bizarre. Do you know of any reasons why or how
setting
path to the root does not work?
HWG hwg-techniques mailing list archives,
maintained by Webmasters @ IWA