You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/08/31 20:22:54 UTC

[jira] Closed: (TAP5-1241) Setting the content length of the response should automatically disable response compression

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

Howard M. Lewis Ship closed TAP5-1241.
--------------------------------------

    Fix Version/s: 5.2.1
       Resolution: Fixed

> Setting the content length of the response should automatically disable response compression
> --------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1241
>                 URL: https://issues.apache.org/jira/browse/TAP5-1241
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.4
>            Reporter: Dan Adams
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.1
>
>
> If if you have Dispatcher (or something else) that generates a response and call response.setContentLength() on a text/* mime type the resulting response content length does not match the length of the actual response. This is due to that you set the content length for the uncompressed content and the response is intercepted and gzipped but the original length is still set. In firefox and IE this doesn't appear to be a problem. Chrome however will simply not load stylesheets where this occurs.
> If something like GZipFilter is going to automatically gzip the response it should also change the content length to reflect the new response length.
> The workaround at the moment is simply not setting a content length.
> This may very well effect future versions; I couldn't find an existing ticket though.

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