Template caching

When configuring user-defined template pages on devices with sufficient memory (e.g., Public Spot gateways), you have the option to cache templates on the device. Caching improves the performance of the Public Spot module, particularly in large-scale scenarios where the device internally caches templates and the HTML pages that were generated from them.

Caching is possible for:

Templates stored in the local file system
Templates stored on external HTTP(S) servers with static URLs

Templates on external servers that are referenced with template variables are not cached on the system.

Enable template caching

In LANconfig under Public Spot > Server > Page table > <Name of the page template>, caching for a page template is enabled by setting Cache page.

The corresponding parameter can be found under Public Spot Module > Page table > Template cache.

Delete template cache

The device automatically deletes or updates the templates stored in the cache once you load a new template file in the file system of your device (for local storage) or when the cache period for an HTTP(S) template runs out (for storage on an external server). The device evaluates the Cache control header of an HTTP(S) template in order to determine the maximum cache period.

Important: If no Cache control header is set, the website is not cached and is immediately discarded. When setting up an individual template, ensure that you combine any META tag with a reasonable cache period (in seconds), for example, <meta http-equiv="cache-control" content="max-age=60">. The duration of the cache period depends on the scenario; there are no specific recommendations.

However, you do have the option of manually deleting the template cache with an action. In the status menu under Public Spot you can do this by starting the action Flush template cache.