Open pboguslawski opened 2 years ago
i think this is an issue with the nested nature of the configuration settings for session, The whole options:
is getting replaced by the admin section. So that means that any 'custom' options added that are not defined in the blueprints is lost.
Currently there is no option for cache_limiter
so that would need to be added here: https://github.com/getgrav/grav/blob/develop/system/blueprints/config/system.yaml#L1375-L1500
When one configures manually session options in system.yaml i.e.
like in
https://github.com/getgrav/grav/issues/1081#issuecomment-377124103
then saving configuration in admin resets it to
and Grav still inserts
in frontend responses when sessions are enabled (required for forms to work) which makes cache headers (Expires, Cache-Control) for Grav pages useless.
Admin plugin should recognize and preserve session.options to allow Grav page caching tuning even for sessions.