CartoDB / cartodb

Location Intelligence & Data Visualization tool

Home Page:http://carto.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Browser cache

jandy1977 opened this issue · comments

Context

Please explain here below what you were doing when the issue happened
Hi.
Browser cache sometimes causes problems when displaying widgets in embed maps.
In general, the browser cache behaves strangely in Carto.
Where in Cartodb to set a permanent token for map display?
It always helps to clear the browser cache.
Thank you very much.
Best regards,
Jan Jandourek.

Steps to Reproduce

Please break down here below all the needed steps to reproduce the issue

Current Result

Please describe here below the current result you got

Expected result

Please describe here below what should be the expected behaviour

Browser and version

What internet browser (Chrome, Firefox, etc) and version was you using and version

.carto file

Don't forget to rename .carto file to .zip file to be able to upload to github

Additional info

Please add any information of interest here below

Not a pro, just a humble user.
I think my problem can also be connected to that issue.
I use docker version (made by Sverhoeven) and run it on my improvised server. I remember having similar problem using regular carto server as well.
I am using carto for a year or so and have noticed that sometimes it has problems with retrieving data from server, as well it has an issue with loading tiles due to invalid token. It might be not working in Chrome if I had loaded that map previously, but may be working flawlessly in Firefox if I load it the first time, and vice versa.
"Invalid or nonexistent map configuration token"
It happens randomly with my maps and I don't quite understand why.
I couldn't also find any ways to reproduce it and to find any workarounds to fix the token. Cleaning browser cache doesn't actually seem to yield any results, token problem seems to stay anyway.
Not only it happens randomly, it also somehow randomly "fixes itself" after some time.

Can you share some workarounds on fixing that token issue?