Quote:
Originally Posted by The Hun
what's in a name...
I mean, if it's in a frame it's not really third party cookie, is it? If for instance thehun.net loads a frame from kinghost.com and kinghost sets a cookie thehun can't get to that cookie without some sort of server side code. So a domain can only get to the cookies it set itself. That's not really third party to me since a third party wouldn't be able to set a cookie for a second party... only on a frame on his own domain.
Now if this whole discussion is based on my literal translation of third party cookies and the term 'third party cookies' means that a domain, no matter how deep in frames it's hidden, can set a cookie on a computer you're right... that can easily be done. No problem
|
"Third party cookie" is a technical term with a precise meaning and it's not what it sounds like. It does not mean a.com setting a cookie to be read by b.com. It means a cookie set by an image, frame, or other object on a domain different from the main page. Do if you frame a page, any cookie set by the framed page is called a third party cookie.
Third party cookies became interesting when ad networks starting using them. A.com would have a banner or frame from adtracker.com. B.com also runs a banner or frame from adtracker.com. With third party cookies allowed, adtracker.com could then track the user across both a.com and b.com. Privacy advocates didn't like that.
__________________
For historical display only. This information is not current:
support@bettercgi.com ICQ 7208627
Strongbox - The next generation in site security
Throttlebox - The next generation in bandwidth control
Clonebox - Backup and disaster recovery on steroids