Avatar for Username

ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

Learn More

Suggestion: Cookie desired retention and cookie rejection on close of browersr

  • 5 პასუხი
  • 1 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 8 ნახვა
  • ბოლოს გამოეხმაურა cor-el

Hi All

I manage my cookies manually as I keep many tabs open permanently. Having to constantly log back in to those accounts would be onerous if cookies were deleted on close of browser. Managing this via manually adding the website exceptions function is also a drag.

Would it be possible to have a 'keep cookie list' that are saved when the browser is closed?

Cheers M

Hi All I manage my cookies manually as I keep many tabs open permanently. Having to constantly log back in to those accounts would be onerous if cookies were deleted on close of browser. Managing this via manually adding the website exceptions function is also a drag. Would it be possible to have a 'keep cookie list' that are saved when the browser is closed? Cheers M

ყველა პასუხი (5)

Seriously dude! Did you even bother to actually read what I have suggested? Streuth....

Kimberl said

I manage my cookies manually as I keep many tabs open permanently. Having to constantly log back in to those accounts would be onerous if cookies were deleted on close of browser. Managing this via manually adding the website exceptions function is also a drag.

Which exceptions function are you using? I'm familiar with two ways to create exceptions to allow sites to set persistent cookies. Those are:

(1) On the Settings page, Privacy & Security panel, Cookies and Site Data section, the "Manage Permissions" button

(2) On the relevant site, the Page Info dialog, Permissions panel -- you can call up Page Info using Ctrl+i (or if the site intercepts that for some reason, Alt+T to drop the Tools menu, then Page Info)

  • When the dialog comes up, click the Permission icon at the top to show that panel.
  • Scroll down to "Set Cookies" and uncheck the "Use default" box, and then select Allow to let the site set persistent cookies.

Probably you are using one of those? Combined with "Delete cookies and site data when Firefox is closed"?

Firefox 102 migrated the "Delete cookies and site data when Firefox is closed" checkbox to the "Clear history when Firefox closes" settings, now that it honors the exceptions list. When using "Clear history when Firefox closes", please make sure NOT to clear "Site Settings" because that category includes your cookie permissions and then you'll need to add them all again.

Would it be possible to have a 'keep cookie list' that are saved when the browser is closed?

How would that be different?

Hi jscher2000 Option 2 there is perfect. Thank you for pointing that out to me. All excellently explained as well. Cheers M

On the relevant site, the Page Info dialog, Permissions panel -- you can call up Page Info using Ctrl+i (or if the site intercepts that for some reason, Alt+T to drop the Tools menu, then Page Info)

When the dialog comes up, click the Permission icon at the top to show that panel. Scroll down to "Set Cookies" and uncheck the "Use default" box, and then select Allow to let the site set persistent cookies. Probably you are using one of those? Combined with "Delete cookies and site data when Firefox is closed"?

Firefox 102 migrated the "Delete cookies and site data when Firefox is closed" checkbox to the "Clear history when Firefox closes" settings, now that it honors the exceptions list. When using "Clear history when Firefox closes", please make sure NOT to clear "Site Settings" because that category includes your cookie permissions and then you'll need to add them all again.

See also my reply in this thread:

It looks that the Stubhub website has a problem with "en-US" in the accept header and with some language combinations gives the "You don't have permission to access..." error. What works is adding a second "en-XX" language or other not English language or if you have "en" as second then add a third language (don't have to be "en-XX" as something like "fr" works).