You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2011/04/22 22:02:05 UTC

[jira] [Commented] (WICKET-3633) content type in header is being lost when using a AbstractTransformerBehavior

    [ https://issues.apache.org/jira/browse/WICKET-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023367#comment-13023367 ] 

Juergen Donnerstag commented on WICKET-3633:
--------------------------------------------

the problem only affects 1.4. 1.5 is using a BufferedWebResponse

> content type in header is being lost when using a AbstractTransformerBehavior
> -----------------------------------------------------------------------------
>
>                 Key: WICKET-3633
>                 URL: https://issues.apache.org/jira/browse/WICKET-3633
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.4.17
>            Reporter: kukushi
>         Attachments: wicket-bug.zip
>
>
> The content type header information is being lost when using a AbstractTransformerBehavior, please see tha attached example of the problem for an example. It isnt causing a problem on my dev box but on live, it is, because the header info is not getting set tomcat/httpd (I'm assuming) is setting the header to plain/text so that the browser ends up showing the html rather than redering it. Here's a bit more information with wget, as you can see with the first call the content info is missing, with the second call without the AbstractTransformerBehavior being called (it's commented out in BasePage) the [text/html] header is included. I debug through wicket code and found that the issue was with the AbstractTransformerBehavior using a StringResponse whose setContentType() (Response.setContentType()) does nothing!!
> ============BUG============
> $ wget http://localhost:8080/wicket-bug/
> --2011-04-22 12:39:19--  http://localhost:8080/wicket-bug/
> Resolving localhost (localhost)... ::1, 127.0.0.1
> Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
> Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 483
> Saving to: `index.html'
> 100%[==============================================================================>] 483         --.-K/s   in 0s
> 2011-04-22 12:39:20 (13.7 MB/s) - `index.html' saved [483/483]
> ============the transformer commented out============
> $ wget http://localhost:8080/wicket-bug/
> --2011-04-22 12:40:27--  http://localhost:8080/wicket-bug/
> Resolving localhost (localhost)... ::1, 127.0.0.1
> Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
> Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 479 [text/html]
> Saving to: `index.html.1'
> 100%[==============================================================================>] 479         --.-K/s   in 0s
> 2011-04-22 12:40:28 (13.3 MB/s) - `index.html.1' saved [479/479]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira