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: 2.0.0-beta, 1.0.0
            Reporter: Michael Freedman
            Assignee: Michael Freedman


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.

Reply via email to