Back to the Proxy Cache section
More websites use a lot of images or large files, the more Webmasters will request the CDN method (Content Delivery Network).
This method aims to load-balance downloads between countries and servers.
For example, Microsoft, Apple and Google updates use this technique.
The proxy service stores objects according to its URL.
Usually this is not a problem, but in the context of CDNs, the subdomain is randomly changed.
For example, a single picture “picture.png” should use 4 urls randomly :
http://cdn1.images.domain.tld/picture.pnghttp://cdn2.images.domain.tld/picture.pnghttp://cdn3.images.domain.tld/picture.pnghttp://cdn4.images.domain.tld/picture.png
while the image is the same.
As a result, the proxy will constantly replace the image on disk and fail to provide the cached image because of these random URLs.
The HyperCache service is designed to respond to this situation by "twisting" the proxy.
Its purpose is to tell the proxy that in our example the prefix is identical.
In this case, it will replace URL as this:
http://cdn1.images.domain.tld/picture.png => http://cdn0.images.domain.INTERNAL/picture.pnghttp://cdn2.images.domain.tld/picture.png => http://cdn0.images.domain.INTERNAL/picture.pnghttp://cdn3.images.domain.tld/picture.png => http://cdn0.images.domain.INTERNAL/picture.pnghttp://cdn4.images.domain.tld/picture.png => http://cdn0.images.domain.INTERNAL/picture.png
The procedure has no effect on the proxy fetch operation. It is just intended to drive the indexing of the proxy's caching.
- HyperCache is materialized by a plugin loaded in memory by the proxy.
You can view its status through the left menu “Caching” > “Status” - You can disable it or enable it using the button in the left section
