Issue Bug Rejected

#91874Cached exceptions with config.contentObjectExceptionHandler

Alexander Vogt 07/27/20, 10:45 updated 06/10/24, 19:08

Description

Prerequisites:
  • config.contentObjectExceptionHandler = 1

When a content exception occurs, the exception will be catched and displayed as “Oops an error occurred.” message. This message gets cached.

This enables users or bots to call a uncached plugin page with invalid action parameters and cause “Oops” messages.
E.g. a bot can call a page like “/de/news?tx_extension_newslist[action]=invalidaction” and cause a “The action “invalidaction” (controller “News”) is not allowed by this plugin / module” exception. To solve this the cache has to be cleared.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.