[
https://issues.apache.org/jira/browse/PLUTO-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Nicklous resolved PLUTO-623.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
this area of code has been rewritten and the issue fixed.
> MimeResponseImpl.getContentType() should check
> PortletMimeResponseContext.getContentType()
> ------------------------------------------------------------------------------------------
>
> Key: PLUTO-623
> URL: https://issues.apache.org/jira/browse/PLUTO-623
> Project: Pluto
> Issue Type: Bug
> Affects Versions: 2.1.0-M3
> Reporter: Eric Dalquist
> Assignee: Eric Dalquist
> Fix For: 2.1.0, 3.0.0
>
>
> getContentType() uses a class member variable to track if a content type has
> been set. The problem is the MimeResponseImpl doesn't monitor the set/add
> property calls which according to the spec can also set HTTP headers
> including the Content-Type header.
> So if I a client sets the Content-Type via a setProperty call and then calls
> getPortletOutputStream or getWriter the MimeResponseImpl will assume no
> content type has been set and set the first value from
> getResponseContentTypes() as the content type, overwriting the previously
> requested value. If MimeResponseImpl checked the
> PortletMimeResponseContext.getContentType it could allow for portals that
> handle all HTTP headers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
