You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Joe Germuska (JIRA)" <ji...@apache.org> on 2007/01/26 21:57:15 UTC

[jira] Updated: (TILES-28) ServletTilesRequestContext always uses include, causing content-type problems

     [ https://issues.apache.org/struts/browse/TILES-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Germuska updated TILES-28:
------------------------------

      Description: ServletTilesRequestContext implements the dispatch() method of TilesRequestContext by always using requestDispatcher.include() which means that requests from the template ("outermost" JSP) to set the content type are disregarded.  It should use requestDispatcher.forward() unless the response is committed.  (was: I haven't gone looking through the code yet, but I have determined that using a TilesResult causes no content-type header to be set.  Using telnet directly to the HTTP server, I can see that a default (ServletDispatcherResult) result forwarding to a JSP sends the correct content-type, but when routing through a TilesResult which has a template which is the same JSP, there is no content-type sent at all.  )
    Fix Version/s: 2.0.0
          Summary: ServletTilesRequestContext always uses include, causing content-type problems  (was: TilesResult loses content-type)

> ServletTilesRequestContext always uses include, causing content-type problems
> -----------------------------------------------------------------------------
>
>                 Key: TILES-28
>                 URL: https://issues.apache.org/struts/browse/TILES-28
>             Project: Tiles
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Joe Germuska
>         Assigned To: Joe Germuska
>             Fix For: 2.0.0
>
>
> ServletTilesRequestContext implements the dispatch() method of TilesRequestContext by always using requestDispatcher.include() which means that requests from the template ("outermost" JSP) to set the content type are disregarded.  It should use requestDispatcher.forward() unless the response is committed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.