Bug #91874
openCached exceptions with config.contentObjectExceptionHandler
0%
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.
Updated by Andreas Kiessling over 1 year ago
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...