Observations:
firstly i used my route without cache control and embedded the svg in github read me -> which results into forever cache of camo server.
I tried many things on the same route but my changes are not received by camo server because they already cached it with old headers
so i changed my route which changes their cache headers for my new server path hence reflecting the changes. 🎉 :)
Yes, once the camo server cached the svg, you will not receive request to increment the counter until the cache is invalid, change server path is a good solution.
Thanks jiang.
I was also trying the counter on my profile
github.com/groverception
Observations:
firstly i used my route without cache control and embedded the svg in github read me -> which results into forever cache of camo server.
I tried many things on the same route but my changes are not received by camo server because they already cached it with old headers
so i changed my route which changes their cache headers for my new server path hence reflecting the changes. 🎉 :)
Hi Anuj,
😸
Yes, once the camo server cached the svg, you will not receive request to increment the counter until the cache is invalid, change server path is a good solution.
I created a configurable visitor counter as well. It beats cache and runs on Azure Functions.
github.com/rahulrai-in/hit-counter-fx