#21569Wrong character encoding in cache tables breaks frontend rendering
Description
There are several issues where cache data makes problems, eg if renderCharset != metaCharset. Then it happens if the cache data has special char like an Umlaut, the returned data is corrupted.
Reason is that cache-table use field TEXT for serialized arrays, therfore MySQL respect the charset.
Solution: use BLOB instead
(issue imported from #M12613)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.