Integrating Perma-Cache with your site

Global Problem: Global Solution

At we present you a global solution to a global problem. With Perma-Cache enabled you do not need to worry yourself about the effects of low cache hit rates anymore, as our simple one click solution takes care of this for you.

How it works

We achieve this by placing our storage as a secondary permanent caching layer between our CDN and your Origin and whenever a request is not cached and would instead be passed to the origin, the CDN looks for it on our storage platform. If it is present, it will pull it from our storage instead - lessening the load on your origin and delivering the file to your users with top performance and speed.

If a file is not found on the storage, the request is then passed normally back to the origin server and returned to the CDN. At the same time, a request is passed to the Perma-Cache system which then asynchronously begins the background caching process. The system connects to your origin server again and downloads the file from your origin to our Geo-Replicated storage. Depending on your replication system, the file is then replicated to our global storage network.

The next time a CDN node will request this file as part of a cache MISS, it will already be available on the storage node and the request will never hit your origin again. The file will effectively be permanently stored in our system.

A cache MISS on the CDN does not 100% guarantee that a file will appear in the Perma-Cache, so we do not suggest using this as a substitute for permanent storage.

This solution is globalized by the use of our GEO replication which replicates the files that are cached on the storage across the world, serving them with optimal speed and increasing their data reliability in case of a localized storage issue.

Perma-Cache Purging

The Perma-Cache also integrates into our file purging API. When a single URL is purged through the API, our system will first send a request to the storage to delete the cached file. After that, the purge request will be processed on the CDN as well and a fresh file will be fetched from the origin again.

When purging the cache for the full Pull Zone cache, the Perma-Cache does not get deleted. Instead, the system switches to a new directory structure within the storage zone. In case of a full purge, you will need to manually delete the old caching folder.

Integrating it with your site

To integrate it with your site, you will first need to have a pull zone created that is pointing to the Origin URL of your site. To create a pull zone, head into the pull zone tab, click "Add Pullzone' and fill out the necessary information.


Afterwards, you need to create a storage zone.


Once both of the above steps are complete, head into your pull zone tab again, select the pull zone you've created and head into the caching tab and then into the Perma-Cache section. Once there, all that remains to be done is select your storage zone and enable the Perma-Cache.


Your site is now successfully configured with our Perma-Cache feature and you will begin to see the size of the Perma-Cache increase soon.

A quick way to check if everything is working as intended, is to check the headers on one of the requests delivered by our CDN. There should be a new header called perma-cache and its status will be either a miss or hit.

I can't see or enable perma-cache

Origin Shield and Perma-Cache are mutually exclusive of each other, meaning you can have only one of the two.

Additionally, if you're using a pull zone connected to our storage, the Perma-Cache option is not available, as you are already hosting your content on our storage. 

If you do need any help, please don't hesitate to contact our support team of Super Bunnies!

Table of Contents

Was this article helpful?
3 out of 4 found this helpful