Split http cache time from one on server

Issue #1 resolved
Andriy Kornatskyy
repo owner created an issue

Problem Statement

The dynamically generated pages may be cached by browser through use of ETag with zero http cache time. The benefit is in generation of 304 response code from server thus no other content is transmitted.


The HTTP1.1 compatible browser. Some proxies act as HTTP1.0 client thus does not supply ETag header which is strong validation token for server.


introduce http_max_age to CacheProfile, check HTTP client version for the feature to work

Comments (2)

  1. Andriy Kornatskyy reporter

    Alternatively if the cached response has etag but the browser didn't supply any than ignore If-Modified-Since request header (the HTTP 1.0 client doesn't supply ETag but still send If-Modified-Since).

  2. Log in to comment