Cookie won't die, it's a cache things I think

I've got a problem with a web site that caches a cookie centrally, causing users of my simple e-commerce site to get wrong shopping baskets. Any ideas why this might be happening

Details
---------
I've got a simple ASP/ SQL Server 2000 web site sitting on a third party host. The site is a very basic b2b web site taking order for materials. I use a cookie to hold the basket number, the basket is in the database.

The problem I'm having is that some of the users are getting old orders or orders that have been placed by someone else in their company. The few HTML pages that are on the site are also being heavily cached, and not updated. I've set everything I can think of to not cache and killed the cookie more times than JFK was shot, and still the problem persists.

As you can tell I think the problem is cookie based but I've never heard of a cookie being cached centrally. Has anyone else experianced this problem? Please not (pride talking) I didn't build this cursed site, I've just been asked to keep it moving. Any help is greatly appreciated.

Would the fact that part of the site from an intranet rather than directly from the internet.

FYI: I am unable to post any code for this problem. I'm just wondering if anyone else has experianced it, and if you've found a solution.

First of all, JFK was only shot twice, so maybe you just haven't tried enough things. Second, you kill cookies by setting their "expires" attribute in the past. Third, don't you think this would be more appropriately posted in the ASP forum since it's a question stemming from that technology and not a general discussion topic?

I've tried killing the cookie a lot more times than twice, just that my history is very bad, I forgot he only got hit twice but shot at three times.

I posted it here as the technology involved is not so simple, as it involves servers, scripting, browsers, and HTTP standards. And I know how much peeps on here hate cross posting. But at your suggestion I will post in the asp, and say I was told to.

go under ur harddrive letter usually known sa "C" drive go in there right click on the "windows" folder and hit delete

to kid_christian90: he is talking about the server side.

to Humble Seeker: Please do not make a second post in the ASP forum. Write to a moderator (For the lounge that´s JCaputo and SilkySmooth) to move the thread.

... IMO your problem is not the cookie. The cookie cannot be replicated among clients. It´s your session management that is broken, it seems to use the same session for all users.

What´s your point?

He's only posted one actual question, everything else has been saying "delete all your files" or other nonsense. *cough*ban*cough*

Thanks Hirsch for the info, I'll look into the sessions management on the server.

Thanks for telling me about asking the moderator unfortunetly I've already posted to the asp forum.

And to the brat kid_christian90 you can't delete the windows directly, well not by simply going to c:\window.

It's possible your IDs are being reused and causing the problems.

Old orders being brought back up:
Try giving a timestamp to each ID in the database and erase ones that have expired. A good time to do that would be when a new ID is requested.

Other customer's orders getting mixed up:
Make sure the ID you generate isn't already being used by another session. Simply picking a random number doesn't guarentee a unique ID.

Other problems:
If your IDs are generated sequentially, it's possible that two different processes may generate the same ID at the same time. Depending on your code, you may want to mark each ID with the process ID or some other marker, then reverify it afterwards to make sure that only that process is using that ID.