When using autoslave, the session information autoslave_affected_tables, creates a session for each request, and therefore causes the cache-control header to be no-cache. This is a problem when anonymous users visits the site, because the page is served from the backend each request.
An idea is to prevent the session information to be set, if the AUTOSLAVE_ASSUMED_REPLICATION_LAG is 0, but this might have other undesired side effects.

Comments

gielfeldt’s picture

gielfeldt commented
Status: Active » Fixed

Hej Rune

Thanks. Now fixed in dev. Session will not be populated if the replication lag parameter is set to 0.

gielfeldt’s picture

gielfeldt commented

... or if there's written to a table which is "always" master (default for session and semaphore).

runand’s picture

runand commented
Status: Fixed » Closed (fixed)