#16533tslib_fe::pageNotFoundHandler does not respect charset settings from localconf or tscript
Description
using pageNotFoundHandling with internal pages does not take care of settings made in localconf.php or typoscript. in my case utf-8 pages are send with defaultCharset iso-8859-1.
i made a little workaround. workaround because i have not found a way to access forceCharset or renderCharset from this function. See Patch below. (I’m sorry, im not able to do CVS/SVN patches. No access from here)
Generate a page with UTF-8 standard. Then set up pageNotFoundHandling to an internal page made in UTF-8. Provoke a 404-error by entering a wrong path to a page. Check out unescaped/specialchared Umlauts for example.
Maybe READFILE and other parameters are affected as well. I did not check that. I’m using Typo3 v4.1 SVN from 2006-08-26
(issue imported from #M4166)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.