8000 Tasks to fix and improve caching · Issue #1389 · contao/core-bundle · GitHub
[go: up one dir, main page]

Skip to content
Tasks to fix and improve caching #1389
@Toflar

Description

@Toflar

As pointed out in other issues already, the caching system still needs a lot of love. We are making good progress but there are still a lot of things to do to make Contao become the CMS with the best native caching support out there. We should not forget that our requirements are very complex and it will remain an ongoing topic that will accompany us for another few versions of Contao.
This issue should serve as a central place to keep track of all the TODO's around the HTTP cache.

Bugfixes

Features

  • We must ensure, we're not starting the session if we don't need it. Starting the session implicitly means that a response is private and may not be cached as it may contain personal information. As long as the core still requires stuff like this, we need to force public responses.

    • $_SESSION['FORM_DATA'] is a real killer here because we never unset the information stored in that value. We must introduce a config option in the form settings to disable that (or enable explicitly). It should be removed in version 5.

    • hasPreviousSession() should be added everywhere we access the session to make sure the session is not started if there's no cookie (Input class) (Only start the session if needed to find data in FORM_DATA #1471) @Toflar

  • We need insert tags as fragments so every insert tag can decide for its own, how it would like to be rendered (and set the correct caching headers) ([RFC] InsertTags as fragments #1470) @Toflar

  • Add support for tagging responses so that we can cache stuff "forever" and invalidate using cache tags. (Use toflar/psr6-symfony-http-cache-store manager-bundle#60) @Toflar

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0