Quote:
Originally Posted by sixsax
You have got to be fucking kidding me. For the third motherfucking time, a frame is a third party object hence cookies set in a frame are THIRD PARTY COOKIES! Any stupid asshole can go Google it to prove you wrong. If you're not trying to manipulate people and it's your developer feeding you this bullshit, fire him on the spot.
|
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