Remove pages.no_cache DB field
The field "no_cache" on pages is very heavy, as it allows editors to completely disable the cache for frontend rendering, not only making heavy use of CPU and allows for more DOS attacks if used wrong.
99.999% of the time, this can be solved differently, e.g. through COA_INT/USER_INT.
[!!!][TASK] Remove DB field pages.no_cache
Having an option to completely disable the page rendering
cache available per page for editors is a real risk. This
option is largely hard to understand for an editor,
or an admin.
Integrators can still use `config.no_cache = 1` in
TypoScript on a condition basis to achieve the same
Tested-by: TYPO3com <firstname.lastname@example.org>
Reviewed-by: Henning Liebe <email@example.com>
Tested-by: Henning Liebe <firstname.lastname@example.org>
Reviewed-by: Susanne Moog <email@example.com>
Tested-by: Susanne Moog <firstname.lastname@example.org>