Some background:
CakePHP writes it\'s own session id cookie besides the PHPSESSID. This is used to authenticate a request. Then an SWFupload sends a file, and that t
Two cookies may have the same name if they were set for different domains or paths.
For instance, if you set a cookie "ID" on "www.example.com" and also on "example.com", then two ID cookies will be sent for every request for "www.example.com" or "anything.www.example.com".
To prevent this, ensure that you're consistently setting cookies for the same domain, and if you happen to have multiple domain names aliased to the same server (e.g. www.example.com and example.com) then have one redirect to the other.
Similarly, don't set cookies of the same name with a different path value.
as far as i remember, if you set a cookie that already exists, it just overwrites the value and expiration date of the old cookie... this is per domain. means you can have 2 cookies with the same name under / and under /anything and they don't overwrite each other.
a cookie's name within it's site is unique. at least in standard. don't know whether IE7 follows this one.
or isn't it what you're asking?
regards