Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Allow a header cookiewhitelist to decide which cookies by third parties are okay to remember

  • 2 Antworten
  • 2 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von cor-el

more options

So i'm a web developer, and cookie laws are getting tighter and tighter because of tracking cookies.

I propose a header a web server can serve that defines whitelisted cookies

cookie_accept: php_session, __utma, __utmz, _ga, _gid

So when I request https://www.foo.bar/baz.html and it has this header and I decide to incorporate 3rd party plugins into baz.html like a facebook button, pinterest button, google maps, YouTube video, that those 3rd party requests done from baz.html will not get sent the cookies the browser has for those domains if the name is not in the whitelist and will not store cookies if the name is in the whitelist.

This way I as a website operator can control what I allow on MY website, instead of being dependent on the whims and cookie law compliance of popular 3rd party websites.

But that requires the support of webbrowsers to obey such a header. Could such a header be made up by the wonderful team behind firefox and perhaps proposed the the w3c to serve as a standard?

So i'm a web developer, and cookie laws are getting tighter and tighter because of tracking cookies. I propose a header a web server can serve that defines whitelisted cookies cookie_accept: php_session, __utma, __utmz, _ga, _gid So when I request https://www.foo.bar/baz.html and it has this header and I decide to incorporate 3rd party plugins into baz.html like a facebook button, pinterest button, google maps, YouTube video, that those 3rd party requests done from baz.html will not get sent the cookies the browser has for those domains if the name is not in the whitelist and will not store cookies if the name is in the whitelist. This way I as a website operator can control what I allow on MY website, instead of being dependent on the whims and cookie law compliance of popular 3rd party websites. But that requires the support of webbrowsers to obey such a header. Could such a header be made up by the wonderful team behind firefox and perhaps proposed the the w3c to serve as a standard?

Alle Antworten (2)

more options

Cookie controls comes from the site and isn't something FF can control or stop. You should contact the site sending the cookies for their support and response to your question.

more options