You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org> on 2007/06/10 18:30:27 UTC
[jira] Updated: (WICKET-356) Detect Content-Type automatically in
ResourceStreamRequestTarget
[ https://issues.apache.org/jira/browse/WICKET-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Quenot updated WICKET-356:
----------------------------------------
Fix Version/s: (was: trunk)
1.3.0-beta1
> Detect Content-Type automatically in ResourceStreamRequestTarget
> ----------------------------------------------------------------
>
> Key: WICKET-356
> URL: https://issues.apache.org/jira/browse/WICKET-356
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Jean-Baptiste Quenot
> Assignee: Jean-Baptiste Quenot
> Fix For: 1.3.0-beta1
>
> Attachments: 20070302-wicket-1.x-ResourceStreamRequestTarget-configure, 20070302-wicket-1.x-ResourceStreamRequestTarget-configure.txt
>
>
> Currently ResourceStreamRequestTarget sets the response Content-Type by getting the value from the IResourceStream, or from the ResourceStreamRequestTarget itself, with a value passed in the constructor.
> I propose to remove the deprecated responseType field, remove the deprecated ResourceStreamRequestTarget(IResourceStream, String) constructor and let the configure() method determine the Content-Type automatically. As a result, IResourceStream instances can return null in getContentType().
> Note that currently, when using the one arg constructor (without Content-Type) and when the JDK does not find a mime-type for the current URI, *Content-Type: null* is being written in the response!!!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.