搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Can we edit how long the cookies are stored?

  • 6 回覆
  • 1 有這個問題
  • 6 次檢視
  • 最近回覆由 ledgeri

more options

Hi!

If i want to manage cookies timewise, i have 3 option: -Store them until they want to be stored -Store them only in session -Do not store them

Is there any option to store them 5 days, 6 hours, 2 weeks, whatever value, then if the FF starts it clears them automaticly?

Hi! If i want to manage cookies timewise, i have 3 option: -Store them until they want to be stored -Store them only in session -Do not store them Is there any option to store them 5 days, 6 hours, 2 weeks, whatever value, then if the FF starts it clears them automaticly?

所有回覆 (6)

more options

Maybe this extension offers that feature:

more options

cor-el said

Maybe this extension offers that feature:

Its old (updated almost a year ago), not really can make it automatic+ i thought there is an editable line in About:Config or something built in...

more options

I checked the builtin Firefox Storage Inspector and I can double-click the Expires field to edit this field and you can edit other fields as well by double-click its value, so you do not need an extension for simple editing. I'm not seeing a mass editing although there is the document.cookie object available in the Web Console.

more options

Sadly the 1by1 method is not a solution... But thanks for the effort!

more options

Hi ledgeri, some sites send set-cookie headers only with the main page, while others may send (update) them with every single file. Therefore, I agree that making a manual change that Firefox doesn't "lock" in any way is not likely to be very effective.

I think you would need an extremely vigilant extension to check every single response in case it needs to modify the header. There may be such an extension, but I haven't heard of one.

Also, what kind of UI would be useful? I'm sure you don't want to return to the bad old days of getting a popup every time a server sets a cookie.

If the goal is to remove some sites' cookies on a schedule, perhaps you might look for an extension that will remove them at a scheduled time rather than trying to modify the expiration dates?

more options

jscher2000 said

Hi ledgeri, some sites send set-cookie headers only with the main page, while others may send (update) them with every single file. Therefore, I agree that making a manual change that Firefox doesn't "lock" in any way is not likely to be very effective. I think you would need an extremely vigilant extension to check every single response in case it needs to modify the header. There may be such an extension, but I haven't heard of one. Also, what kind of UI would be useful? I'm sure you don't want to return to the bad old days of getting a popup every time a server sets a cookie. If the goal is to remove some sites' cookies on a schedule, perhaps you might look for an extension that will remove them at a scheduled time rather than trying to modify the expiration dates?

I thought since the last acces is noted in the management of cookies, a fast chechk would run at start up/ shut down, to check the date of last access, and if it more than the set value, it needed to be deleted. UI no more than a slider, or open field to set days/hours.. Or even a line in about:config... It would be usefull for basic privacy, but also in cases when a mobile device lost/stolen, but basicly not protected well by passwords, but kinda with built in time lock.

Yeah, the direction would be an overal maximum, an overall time lock, and not a cookie editing script.

For me the current stage is a bit strange because there is no middle ground: Session cookies and "cookies deleted after session" or "whatever the website wants..."

At least it cleared out to me... Thanks for the comments! I have a lot yet to be learned :)