You should have 3 cookies when you look at the cookie info for the thread index of this forum. (According to WebDeveloper, anyway)
Always wished there was some way to decipher or look up on the host site what the "Content:" value was supposed to convey.
It's not that huge of a deal (In most cases, I hope), but it's always felt kind of covertly suspicious to me that we can't know what any cookie does, exactly, when it's on OUR systems, influencing and exerting control over OUR experiences.
If I ruled the web, cookie information, value parsing, and all behaviorswith plain-language interpretationswould be something every site that uses them would be required by law to make conspicuously available to visitors.
>If I ruled the web, cookie information, value parsing, and all behaviorswith plain-language interpretationswould be something every site that uses them would be required by law to make conspicuously available to visitors.
remind me not to shop with a credit card on your web. :P
The cookie info I speak of should be visible to each of us, individually, not to OTHER users, unless the values and behaviors for that cookie is something generic or common to all visitors who accept the cookie(s) from a particular site.
I want to know what info the cookies on MY system contain, and what behaviors they exhibit...on MY system. I don't care about what the cookies do on somebody else's system.
I don't wish to share my cookies with others. If they were decipherable by just anyone. Then just anyone could alter them to do all kinds of Damage. We already have nough problem on the internet with Active-X controls.
How is someone going to alter a cookie that is stored on your machine ... if someone can access your computer remotely, you have way bigger problems than a bad cookie (which is a harmless text file that cannot run code).