Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 342242

Summary: Consider to remove the ability to compress responses from RWT
Product: [RT] RAP Reporter: Rüdiger Herrmann <ruediger.herrmann>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: 1.4 M7   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 341763, 342672    
Attachments:
Description Flags
Fix none

Description Rüdiger Herrmann CLA 2011-04-08 04:27:00 EDT 
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.
Comment 1 Ralf Sternberg CLA 2011-04-11 05:36:22 EDT 
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.
Comment 2 Rüdiger Herrmann CLA 2011-04-18 05:38:07 EDT 
Created attachment 193470 [details]
Fix

Removes gzip compression for Javascript library requests and normal life cycle requests
Comment 3 Rüdiger Herrmann CLA 2011-04-18 05:38:59 EDT 
Applied patch to CVS HEAD