-
Bug
-
Resolution: Fixed
-
Minor
-
3.2.9, 3.3.0
The Content-Type response header of atom feeds does not include the charset so content encoding may be misinterpreted. The controller calls setCharset but this call only works with Content-Type headers which start with text/. Just put the character set part in the Content-Type header directly.