Bug #83676

Epic #83652: EXT: Redirects module - Umbrella issue

EXT:redirect Add limitations to documentation

Added by Stefan Froemken over 3 years ago. Updated almost 3 years ago.

Should have
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


Hello Core-Team,

thank you for EXT:redirect. It looks pretty good.

As you retrieve ALL valid redirects from CachingFramework, which is configured to use MySQL DB, you have a limitation in column "content", which is configured to mediumblob. This column can save up to 16MB.

A little calculation:

16MB * 1024 * 1024 / 258 (Bytes per record) = ~65.000 redirect records

I'm nearly sure, that nobody will have such a mass of redirect records, but I think we should document that limitation for users. It should also be documented how to solve that problem by configuring CF to use f.e. SimpleFileBackend

Nice greetings



Updated by Susanne Moog over 3 years ago

  • Parent task set to #83652

Updated by Tymoteusz Motylewski over 3 years ago

I'm nearly sure, that nobody will have such a mass of redirect records

I'm pretty certain that many installations will have much more redirects.
Please take into account that in the longer run we will store not only manually created redirects, but also automatically generated ones.
E.g. when page title or news title changes, new url is generated and a redirect is created.

I saw installations with realurl tables with millions rows => the same will happen here.


Updated by Mathias Schreiber over 3 years ago

  • Status changed from New to Resolved

Resolved with the 9.1 documentation.
Thanks for the math :)


Updated by Benni Mack almost 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF