Version aliasing doesn't point to the latest version about libgrabber HOT 7 CLOSED

We have the latest version http://www.jsdelivr.com/#!algoliasearch so its not a libgrabber problem.

For version aliasing to offer performance bonus we need to cache it for a certain amount of time, thats why its not instant after update. The cache should expire soon automatically.

And once we setup a purging API we can work more on that and make our bot to automatically purge the cache when a new version is added.

But we always were and will be recommending to use full versions in your URLs. Its the safest and fastest solution.

from libgrabber.

Thanks for details.
Can you tell me more about your caching policy, please: how long are resources behind aliases cached? When are you planing to have this purging API that could be used every time a new version is pushed?

Thanks,

from libgrabber.

In the next month I will try to have the purging API ready. Of course its going to be accessible only by our bots.

Right now the CDN caches static files for 12 months.
/g/ is cached for 6 months
2 from 2.0.3 is cached for 1 month
latest is cached for 2 weeks

from libgrabber.

Alright thanks for detail.
Looking forward to see this purging API live :-)

Cheers,
Alex

from libgrabber.

np, let me know if you have any questions or any other feedback

from libgrabber.

I assume 2.0 from 2.0.3 is cached for 1 month also?

from libgrabber.

yes, its the same thing

from libgrabber.