[OSM-dev] How can I force refresh of map tiles after move to a new backed?

[Maarten Deen]

On 2020-12-29 10:27, Tom Hughes wrote:
> On 29/12/2020 09:14, Maarten Deen wrote:
> 
>> Recently I have had more occasions where I updated something and I 
>> kept seeing the old version and I had to use CTRL-F5 to see the new 
>> version. In the past just a reload (CTRL-R) was sufficient. I wasn't 
>> aware that there was a new backend. If this is related to that I would 
>> like to ask that this is looked at as to why this happens.
> 
> I'm not aware of the details of your OS and browser so I can't comment
> on specific key combinations.

Firefox on windows 7.

> Specifically I don't know if Ctrl-F5 is any different to Ctrl-R in your
> environment, but a simple Ctrl-R reload has never done anything other
> than reload, using whatever cached results are available. In most cases
> that won't go to the server at all it will just reuse the tiles the
> browser already has.
> 
> A forced reload (typically Ctrl-Shift-R) is what forces the browser to
> check with the server, and to request that any caches in the path try
> to revalidate with their upstream.

I've looked it up and the internet says "CTRL-F5 does a force cache 
purge where CTRL-R does not"
https://superuser.com/questions/205279/ctrlf5-vs-ctrlr-on-browsers

In the past I have always used CTRL-R to refresh and generally within a 
few minutes the new tiles were shown. As I said, the last few days I've 
had edits where this did not do anything and only with a CTRL-F5 I saw 
new tiles.
So from my perspetive, the behaviour of the map has definitely changed.

Regards,
Maarten