#91874Cached exceptions with config.contentObjectExceptionHandler
Description
- 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.
History 2
-
Andreas Kießling commented 09/29/22, 10:52
-
Georg Ringer commented and changed status
NewRejected 06/10/24, 19:08I am closing this issue because of the following reason:
with latest typo3 versions and strict chash validation this should not be an issue any more as attackers can not forge url parameters without running into a 404
feel free to contact me via slack or open a new issue if you don’t agree
Hey Alexander,
did you find any workaround for this? Bingbot seems to like one of my projects a lot and crawls with a massive amount of invalid urls / params and makes this error quite a PITA…
Update: enabling callDefaultActionIfActionCantBeResolved for my plugin seems to bypass the error – maybe this should be the default then…