We have the foundation of a middleware that can deflate responses, although it's still incomplete.
Only compress response when client can handle our compression methods
* * *
It won't build if I only commit half of the files...
* * *
Missing this one too
Clarify behaviour of server regarding chunked transfer encoding
Do not chunk response bodies
SiteMesh middleware no longer chunks responses that are not decorated
NotFound middleware now uses charset of response, instead of ISO-8859-1
Failsafe middleware now uses response encoding instead of iso-8859-1
Use the binary content of the buffer rather than its chars when rendering non decorated content
Clarify that we're checking if response should be decorated
It's both more robust and more flexible to buffer response before compressing
If I get confused, I should clarify the api
Remove content length header of compressed responses
Silence the anoying jmock synchronisation warning (no clue why JMock thinks this is running in a thread)
Fix compression issue. Can't manage to write a failing test for this.
Don't set zlib headers, which cause some http client to choke. And use the deflate stream, it's much simpler and less prone to errors