Want to hire a development team?
No Images Added Yet

Implementing Cross-Domain Cookies

Rated4.0/5 (4 ratings)
Add to Favorites
Describes a solution to using the same cookies for multiple domains.
Product Details

According to the cookie specification, any cookie set for one domain, must not be sent to any other domain. Therefore, if you set a cookie in your user's browser on one domain, that cookie will not be available on any other domain. This tutorial describes a solution to get around this issue.

Report this Listing
Licence Type
Submitted on
30th November 2000
Last Updated
11th February 2009

You May Also Like

User Reviews

Please rate the listing and tell the world know what do you think about the listing.
(4 ratings)
Average User Rating: 4.0/5
Good but not good enough for general use
Reviewed byAnonymousonTue, 30th April 2002
Rating 3 - Average
His solution is web-server implementation-specific, and as a result is no solution for those who use something besides Apache. As well, any solution that requires too many pieces to successfully interact is a fragile solution when it comes to web implementations. Asynchronous foot races tend to develop between all the pieces of the solution that are supposed to be serialized and well-behaved, if for no other reason than the internet infrastructure is not aware of the whole logical framework of the intended interaction ... each router, each server is just busy pushing packets and bytes from many sources to many desinations at any one instant. A more elegant solution would be to pass information between cross-domain apps as an extra header or two that are then stored and referenced by the target app. More than one less-than-honorable user has been known to turn off javascript / java / activex in the middle of a transaction in order to gain some advantage / cause some havoc / evade detection, etc. Then where does your information go ?
Displaying 1-1 out of 1 reviews
View All Reviews