Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1241

Setting the content length of the response should automatically disable response compression

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.4
    • Fix Version/s: 5.2.1
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      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.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              hlship Howard Lewis Ship
              Reporter:
              hagios17 Dan Adams

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment