9
The scenario of my problem is this, I have a website that has been updated, but some customers are reporting that the update was not made for them, which are still in the old model of the site (probably by the persistence of cache).
I’ve done several updates and never had that problem. I don’t know if it was the size of the update (basically a re-work of the whole project) that is implicating this problem, but I can’t get users to access the new version of the site.
I know to clean up the cache, Ctrl+F5, Ctrl+r may help, but not feasible...
I already make use of the version practice in the files, for example:
scr="meuscript.js?v=0123456"
href="meuestilo.css?v=0123456"
I also use some tags in HTML, such as:
<meta http-equiv="Cache-Control" content="no-cache" />
<meta http-equiv="Pragma" content="no-cache" />
<meta http-equiv="Expires" content="0" />
But nothing has produced the desired effect. I confess that it is an area that I do not possess much experience and knowledge. So, what could I do to get the desired result? That is, force the page update (or cache) on the client side?
a dummie parameter in the url does this...
– andrepaulo
@andrepaulo some example?
– celsomtrindade
if your url has no parameter
?a=1
for example... if you have&a=1
see if it helps you... but every time Voce wants updated the number changes, or the parameter changes... each different url causes the browser to update– andrepaulo
@andrepaulo was not the case... Remains the same thing.
– celsomtrindade
Question: Have you entered the tags before or after cache control problem appears? If it was later, it would take clearing the cache to update them to the version with these tags.
– Woss
@Andersoncarloswoss I started using from this update. That is, in the previous version did not exist and this exists. But even so, it wouldn’t make the file read differently?
– celsomtrindade