Since most people do not change their ENS info that often, this is not a big issue. However, I was experimenting with returning a random variation of my orchestrator icon on each request, which does not work as it keeps the old icon cached for a long time
I can understand that reducing the Cache-Control value by too much isn't desirable (for my use case as low as possible would be best), but maybe we can reduce the cooldown to a couple of hours?
Currently changes in ENS take a while to propagate, due to the
Cache-Controlheader being set to one day:https://github.com/livepeer/explorer/blob/7bc21acbd17249f00b70558e984a8c2528b92609/pages/api/ens-data/image/%5Bname%5D.tsx#L14
Since most people do not change their ENS info that often, this is not a big issue. However, I was experimenting with returning a random variation of my orchestrator icon on each request, which does not work as it keeps the old icon cached for a long time
I can understand that reducing the
Cache-Controlvalue by too much isn't desirable (for my use case as low as possible would be best), but maybe we can reduce the cooldown to a couple of hours?To compare: cached image vs actual image, which has a expiry of -1 in nginx