[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-166.
--------------------------------------------
Fix Version/s: 1.0.1
2.0.0
Resolution: Fixed
Did as suggested.
> Bridge header management tries to ensureContentType header but can result in
> incorrect ContentType
> --------------------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-166
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-166
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 1.0.0, 2.0.0-beta
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 1.0.1, 2.0.0
>
>
> Problem is it blindly appends the request's charset to the content-type. I
> have run across at least one situation where the CT already a charset --
> resulting in two in the generated CT -- an invalid representation. Prune the
> existing one first (in case its incorrect) and then append the request's.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
