We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Este fío arquivouse. Faga unha nova pregunta se precisa axuda.

Force sync of cookies in memory to sqlite. Or, disable the cookie cache

  • 5 respostas
  • 2 have this problem
  • 1 view
  • Last reply by PJAL

PJAL
PJAL
more options

I do not know the mechanics of when FF updates cookies to the cookies.sqlite DB. Some articles claim that cookies are only saved to the sqlite DB on session close. However, I have found that cookies do get updated to the sqlite DB before the session is closed. However, this is not consistent. The behavior is unpredictable when writing and deleting cookies within short time spans.

I have attempted to use the meta tag to force the html to not cache data but this doe not work. (This would be a nice feature if it worked since I could selectively sync just cookies related to the required pages thus reducing overhead.)

<meta http-equiv="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="no-cache"> <meta http-equiv="Expires" CONTENT="-1">

I do not know the mechanics of when FF updates cookies to the cookies.sqlite DB. Some articles claim that cookies are only saved to the sqlite DB on session close. However, I have found that cookies do get updated to the sqlite DB before the session is closed. However, this is not consistent. The behavior is unpredictable when writing and deleting cookies within short time spans. I have attempted to use the meta tag to force the html to not cache data but this doe not work. (This would be a nice feature if it worked since I could selectively sync just cookies related to the required pages thus reducing overhead.) <meta http-equiv="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="no-cache"> <meta http-equiv="Expires" CONTENT="-1">

Chosen solution

Several issues with cookie behavior. Since there is no sync there is not a good way to know what is stale data. Furthermore, when the same cookie is deleted and then rewritten and read back to the originating page there is a string of cookies listed under the same name. They are the previous cookies that were to be deleted.

I believe using sessionstorage will fulfill my need which is to simply inspect and confirm back end user (cookie) data. I will also be evaluating moving away from cookies and to appstorage.

Ler a resposta no contexto 👍 0

All Replies (5)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Firefox stores cookies separately from the memory cache or disk cache, which are for web pages and selected files.

The SQLite database component may store some changes in temporary files before committing them to the database (see https://sqlite.org/tempfiles.html). I don't know if you can exercise any control over that.

Could you describe what you're trying to do in more detail?

PJAL
PJAL Question owner
more options

Set some new cookies and they did not show up in either .sqlite.wal or .sqlite.shm.

I have looked into local storage and this might be an alternative solution.

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Is there a functional issue with the cookies not being returned to the site after being set, or is it just troubling that the cookies are not committed to disk in a timely manner?

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Maybe you can force Firefox to save the cookies to cookies.sqlite by opening a private browsing window as that should make Firefox save all data to the profile folder and switch to in memory storage.

PJAL
PJAL Question owner
more options

Chosen Solution

Several issues with cookie behavior. Since there is no sync there is not a good way to know what is stale data. Furthermore, when the same cookie is deleted and then rewritten and read back to the originating page there is a string of cookies listed under the same name. They are the previous cookies that were to be deleted.

I believe using sessionstorage will fulfill my need which is to simply inspect and confirm back end user (cookie) data. I will also be evaluating moving away from cookies and to appstorage.