By using an HTTP cache, it is possible for us to handle a six-digit amount of concurrent visitors to a Ruby-backed website.
HTTP Caching is disabled by default. Please contact our operations team to enable it for your application. Once activated, the configuration the load balancer will interpret the Cache-Control Header Show archive.org snapshot . You have to set this header correctly in your application in order for the caching to work. If this is not possible for some reason we can setup a special configuration for your caching (see below).
Cache-ControlHeader to public and
max-ageto an appropriate value.
Cache-ControlHeader to one of these values (depending if the clients should be allowed to cache):
Set-Cookiewill not be cached
Set-CookieHeader responses are cached with the default maximum settings (see next point)
Cache-Controlheader are honored) and will only store responds with HTTP 200 or 404 (for 1 minute).
PragmaHeader is not honored by default but can be enabled on request.
X-Proxy-Cacheheader for responses so that you can see which requests were really cached.
Cache-Key) differ by the requested hostname and URI (including parameters). If your website returns different content for e.g. mobile and desktop user agents we need to configure this.
The configuration options in our default setup should be suitable for the most use cases. However sometimes the configuration needs to be adjusted. There are many solutions for special requirements on caching but you can have a look at these examples of possible configuration:
If you are not sure what is suitable for you don't hesitate to contact our operations team.