3 ms·
They should both pay a bounty. But if you had to assign blame only one place it would be ECMAscript. Setting the value of an unintended cookie should not be so
by brlewis 12y ago
They should both pay a bounty. But if you had to assign blame only one place it would be ECMAscript. Setting the value of an unintended cookie should not be so easy to do by accident.
- ycitm 12y agoNitpick: strictly speaking setting cookies is not part of ECMAScript, it's part of the DOM api.
- billyhoffman 12y agoCookies are, without a doubt, the worst "API" in the DOM. Here's the entire API: document.cookie That's it. That one property.To add cookies, modified cookies, delete cookies, whatever, you do an assignment. To read all the cookies, you do a read. That's it. That's the API.
- sarciszewski 12y agoThis is correct, and it's a source of madness. One more thing: Cookies are limited to 4KB total due to the HTTP/1.1 specification.