[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-dev
Subject:    [jira] Updated: (TAP5-1241) Setting the content length of the
From:       "Howard M. Lewis Ship (JIRA)" <jira () apache ! org>
Date:       2010-08-31 18:09:53
Message-ID: 2714773.97041283278193972.JavaMail.jira () thor
[Download RAW message or body]


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

Howard M. Lewis Ship updated TAP5-1241:
---------------------------------------

    Summary: Setting the content length of the response should automatically disable \
response compression  (was: Automatic gzipping does not allow setting a content \
length for generated content)

> 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
> 
> 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.


[prev in list] [next in list] [prev in thread] [next in thread]