--- Nicole <[EMAIL PROTECTED]> wrote: > <img src=http://thetrackingurl/?param1=val1¶m2=val2&etc...
[snip] > The tracking site is different from the site that the product is sold on. > > A cookie was placed on the client's (buyer) side to store where that > client originated from. So when the hidden image is called, the > tracking script is called and tries to access this cookie to retrieve > where the buyer came from. I think I understand now. I think you are understanding everything except how a request is made for an embedded resource such as an image. These requests are identical to the requests for the parent resource. First, let us make up some domains, so that this is clear: 1. store.org - where the user is making the purchase 2. track.org - where the image is located The cookie is being set as the user is browsing store.org, correct? As such, it will only be sent in future requests for resource within store.org's domain. When the browser requests the image from track.org, the domain is different, so the cookie is not sent. This is no different than why cookies for php.net aren't sent to amazon.com. Hope that helps. Chris ===== Become a better Web developer with the HTTP Developer's Handbook http://httphandbook.org/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
