Issues with cookies and upgrade #16673
Unanswered
whoacowboy
asked this question in
CLI - PWA mode
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I recently launched my site using Quasar as the FE. I don't think this is specific to Quasar but more of a SPA issue.
I am having some major issues with the site accessing stale code, JWT token and other 3rd party cookies.
For the stale code I came up with a script that keeps the last four versions of the code live on the server when I publish. This works OK, but it I will still get the occasional errors after publishing.
For the JWT token I ended up changing the cookie's name of the token on the FE, which works OK but still doesn't feel ideal.
The last issues is difficult for me, I am using CloudFront to secure some of the assets on my site. I am unable to use the rename strategy because AWS is looking for those specific cookies.
One of the main pieces of advice I have received is to add
Add "Cache-Control": "no-cache" to index.html on the server.
Unfortunately I am using a DigitalOcean and it only posts the site to a static server that doesn't have that option. I was hoping to avoid moving the site to another server but will do that if I must.
Any ideas you might have are appreciated.
Beta Was this translation helpful? Give feedback.
All reactions