Closed Bug 535335 Opened 15 years ago Closed 12 years ago

Investigate policy of having a separate third-party cookie for each first-party context

Categories

(Core :: Networking: Cookies, enhancement)

Product:
Core
Component:
Networking: Cookies
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 565965

People

(Reporter: gerv, Unassigned)

Details

If disabling third-party cookies entirely breaks too much of the web, another suggestion is to have a separate third-party cookie for each first-party context. So you have one foo.com cookie for each site which has third-party content from foo.com. This might allow services to work while stopping Foo Corp tracking you across sites.

There are a number of possible issues with this, but I think we could experiment with it in development builds to see how much of the web broke.

(This would clearly significantly increase the number of cookies stored.)

Gerv
More discussion over in bug 565965, so duping.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.