Project: Tomcat
Bug 39572 fixes to use CompressionFilter in WebSphere app server
Reported: 2006-05-12 22:28:57 | Status: resolved fixed

There are a couple of small bugs in the compression filter classes that are triggered by using the filter in WebSphere 5.1 or 6. Here are patches. - CompressionResponseStream should not compress the output stream if the response has been committed (because then it cannot write the Content-Encoding: gzip header, and the browser displays the compressed output as-is) - CompressionServletResponseWrapper causes a NullPointerException if you flush before writing anything

Files changed in fix:
webapps/examples/WEB-INF/classes/compressionFilters/CompressionFilterTestServlet.java webapps/examples/WEB-INF/classes/compressionFilters/CompressionResponseStream.java webapps/examples/WEB-INF/classes/compressionFilters/CompressionServletResponseWrapper.java