Community
Participate
Working Groups
Previously, RWT compressed all of its responses. Since, under some circumstances, compressing responses led to invalid output (bug 259977), it was made configurable (bug 285669). In general, compressing reponses and the decision when to compress should be handled by the servlet engine. All major servlet engine implementations offer such features, hecne I propose to remove the response compression from RWT entirely.
I fully agree with this proposal. We've already agreed to register the concatenated JavaScript as a resource (bug 335545). Those are the largest chunks of code to be delivered to the client. Since static resources cannot be compressed by RAP anyway (as we can't set headers for them), the only remaining responses to be compressed are the lifecycle responses. The majority of these lifecycle responses are rather small and don't need to be compressed.
Created attachment 193470 [details] Fix Removes gzip compression for Javascript library requests and normal life cycle requests
Applied patch to CVS HEAD