Table of contents
- Caching dynamic content
- Domain mode
- Domains externally registered
- Email antispam
- Email client configuration
- Email out-of-office assistant
- Email sending with PHP
- Email sending with Wordpress
- Python Packages
- Python memory requirements
- SSH access
- SSH tunnel
- Secure downloads using X-Accel-Redirect
- Technical limitations
Confused?If there is anything unclear, please contact us. We are always glad to help.
Caching dynamic content
In order to cache dynamic content of a PHP or Python application you need to configure your domain as follows:
WSGI/PHP URI "/" points to the "WSGI application" or the "PHP container" Choose the maximum time that you want content to be cached in the cache dropdown.
By default all responses (HTTP status codes 200, 301, 302 and 404) of the application are cached. For security reasons responsens to requests with a cookie set or responses that set a cookie are never cached.
Various Cache-Control headers are respected for fine tuning the cache. It is possible to set a shorter cache time or disable the cache entirely. This is important for dynamically generated captcha images.
In order to disable the cache for a single response set the following cache headers:
response['Cache-Control'] = 'no-cache'
Furthermore the following headers are supported:
Expires: XXX Cache-Control: no-cache Cache-Control: max-age=XXX Cache-Control: private Cache-Control: no-store
Currently there is no way to remove an element from the cache. In order to circumvent this we recommend the use of URLs that contain version information.
e.g. a dynamically generated file "sitemap.xml", which you want to cache for performance reasons could be made available via the following file name schema: http://example.com/sitemap-YYYYMMDD.xml
For files that are not changed often a more simple versioning scheme could be more appropriate. e.g. "style-v1.css"