You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Eric Dalquist (JIRA)" <pl...@jakarta.apache.org> on 2004/11/15 18:03:23 UTC
[jira] Created: (PLUTO-84) RenderResponse mime-type wildcard matching is not done
RenderResponse mime-type wildcard matching is not done
------------------------------------------------------
Key: PLUTO-84
URL: http://nagoya.apache.org/jira/browse/PLUTO-84
Project: Pluto
Type: Bug
Components: portlet container
Versions: Current CVS
Environment: Tomcat 5.0.28
Reporter: Eric Dalquist
The setContentType method of RenderResponse calls an internal method isValidContentType(String) to check to see if the mime type being set is valid. This method doesn't do wildcard matching if wildcards are specified in the portlet.xml supports tags. For example the following does not allow the portlet to use any mime-type:
<supports>
<mime-type>*/*</mime-type>
<portlet-mode>view</portlet-mode>
</supports>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (PLUTO-84) RenderResponse mime-type wildcard matching is not done
Posted by "Nick Lothian (JIRA)" <pl...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/PLUTO-84?page=history ]
Nick Lothian closed PLUTO-84:
-----------------------------
> RenderResponse mime-type wildcard matching is not done
> ------------------------------------------------------
>
> Key: PLUTO-84
> URL: http://nagoya.apache.org/jira/browse/PLUTO-84
> Project: Pluto
> Type: Bug
> Components: portlet container
> Versions: Current CVS
> Environment: Tomcat 5.0.28
> Reporter: Eric Dalquist
> Assignee: Nick Lothian
> Fix For: Current CVS
>
> The setContentType method of RenderResponse calls an internal method isValidContentType(String) to check to see if the mime type being set is valid. This method doesn't do wildcard matching if wildcards are specified in the portlet.xml supports tags. For example the following does not allow the portlet to use any mime-type:
> <supports>
> <mime-type>*/*</mime-type>
> <portlet-mode>view</portlet-mode>
> </supports>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (PLUTO-84) RenderResponse mime-type wildcard matching is not done
Posted by "Nick Lothian (JIRA)" <pl...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/PLUTO-84?page=history ]
Nick Lothian updated PLUTO-84:
------------------------------
Fix Version: 1.0.1-rc2
(was: Current CVS)
> RenderResponse mime-type wildcard matching is not done
> ------------------------------------------------------
>
> Key: PLUTO-84
> URL: http://nagoya.apache.org/jira/browse/PLUTO-84
> Project: Pluto
> Type: Bug
> Components: portlet container
> Versions: Current CVS
> Environment: Tomcat 5.0.28
> Reporter: Eric Dalquist
> Fix For: 1.0.1-rc2
>
> The setContentType method of RenderResponse calls an internal method isValidContentType(String) to check to see if the mime type being set is valid. This method doesn't do wildcard matching if wildcards are specified in the portlet.xml supports tags. For example the following does not allow the portlet to use any mime-type:
> <supports>
> <mime-type>*/*</mime-type>
> <portlet-mode>view</portlet-mode>
> </supports>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (PLUTO-84) RenderResponse mime-type wildcard matching is not done
Posted by "Nick Lothian (JIRA)" <pl...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/PLUTO-84?page=history ]
Nick Lothian reassigned PLUTO-84:
---------------------------------
Assign To: (was: Nick Lothian)
> RenderResponse mime-type wildcard matching is not done
> ------------------------------------------------------
>
> Key: PLUTO-84
> URL: http://nagoya.apache.org/jira/browse/PLUTO-84
> Project: Pluto
> Type: Bug
> Components: portlet container
> Versions: Current CVS
> Environment: Tomcat 5.0.28
> Reporter: Eric Dalquist
> Fix For: 1.0.1-rc2
>
> The setContentType method of RenderResponse calls an internal method isValidContentType(String) to check to see if the mime type being set is valid. This method doesn't do wildcard matching if wildcards are specified in the portlet.xml supports tags. For example the following does not allow the portlet to use any mime-type:
> <supports>
> <mime-type>*/*</mime-type>
> <portlet-mode>view</portlet-mode>
> </supports>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (PLUTO-84) RenderResponse mime-type wildcard matching is not done
Posted by "Nick Lothian (JIRA)" <pl...@jakarta.apache.org>.
[ http://nagoya.apache.org/jira/browse/PLUTO-84?page=history ]
Nick Lothian resolved PLUTO-84:
-------------------------------
Assign To: Nick Lothian
Resolution: Fixed
Fix Version: Current CVS
Modified RenderResponseImpl.isValidContentType to correctly handle wildcard mime types
> RenderResponse mime-type wildcard matching is not done
> ------------------------------------------------------
>
> Key: PLUTO-84
> URL: http://nagoya.apache.org/jira/browse/PLUTO-84
> Project: Pluto
> Type: Bug
> Components: portlet container
> Versions: Current CVS
> Environment: Tomcat 5.0.28
> Reporter: Eric Dalquist
> Assignee: Nick Lothian
> Fix For: Current CVS
>
> The setContentType method of RenderResponse calls an internal method isValidContentType(String) to check to see if the mime type being set is valid. This method doesn't do wildcard matching if wildcards are specified in the portlet.xml supports tags. For example the following does not allow the portlet to use any mime-type:
> <supports>
> <mime-type>*/*</mime-type>
> <portlet-mode>view</portlet-mode>
> </supports>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira