The current Omniture "opt out cookie" is set to expire in 2010. Let's set it to something a bit longer like 2018. Since this site I believe is maintained by Omniture, we may need to send the request to them.
Assigning to Jeremy to ensure we don't lose track of this.
Sent e-mail to Caleb.
Am I looking at the wrong thing? This doesn't seem fixed to me, since the cookie's expiration date is still only two years out--2010.
Created attachment 337830 [details] 2010 cookie expiration I can confirm what Stephen is seeing as well - looks like the cookie is expiring in 2010 not 10 years per the request. Re-opening.
I've pushed the change to prod and it should be live within the next hour.
I don't want to jump the gun, but I'm still seeing the cookie's value set at 2010, and it's a couple hours later -- has some cron job just not yet run?
It's working for me. Did you clear your existing cookies?
I can verify that this is not working for me either. I checked that I have no " cookies with "opt" in the string. Installed the opt out cookie and it shows 2010.
Still waiting for omniture to respond.
Omniture says that the timing for the opt-out cookie expiration is 2 years and can't be changed (e.g., to 10 years as Basil had requested). Is this a problem for us?
We never mention the length of expiration of the cookie on any of our web pages but in the discussion we had in mozilla.governance, we stated that we would do that. So, it's a tacit commitment. On the other hand, if it can't be done - then what? We can 1) pressure Omniture or 2) live with it or 3) toss out Omniture. :-)
Omniture says this this not possible.
(In reply to comment #13) > We never mention the length of expiration of the cookie on any of our web pages > but in the discussion we had in mozilla.governance, we stated that we would do > that. So, it's a tacit commitment. On the other hand, if it can't be done - > then what? We can 1) pressure Omniture or 2) live with it or 3) toss out > Omniture. :-) Actually, we do on http://www.mozilla.com/en-US/opt-out.html, so I've filed bug 461608 to deal with that.