[TYPO3-core] RFC: #4379 - pageNotFound_handling ignores forceCharset setting

[Michael Stucki]

This is a SVN patch request.

Problem:
If $TYPO3_CONF_VARS[FE][pageNotFound_handling] is triggered and pointing to
an URL, TYPO3 ignores the setting of $TYPO3_CONF_VARS[BE][forceCharset ]
and outputs a wrong charset in the header.

Solution:
- Add support for multy-line $header parameter in
  tslib_fe::pageNotFoundHandler()

- Fetch also the headers of the 404 document

- Forward only those headers that are specified in $forwardHeaders
  (currently this is only the Content-Type which usually contains the
  charset on the same line).

Branches: TYPO3_4-0 and Trunk

Bugtracker reference:
http://bugs.typo3.org/view.php?idC79

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug_4379_v2.diff
Type: text/x-diff
Size: 1905 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20061107/c4a1eec3/attachment.bin