users@glassfish.java.net

Re: Double compression conundrum

From: <glassfish_at_javadesktop.org>
Date: Thu, 18 Dec 2008 05:38:13 PST

Looking at the grizzly source it was seen that "Content-Encoding" set to "deflate" or "gzip" are not equivalent. In particular, if the header contains "gzip" grizzly unconditionally skips the compression filter, but if it is "deflate" it does not.

I guess "gzip" is the defacto standard for http 1.1, but it appears to be a simple bug that "deflate" is also not recognized.

So switching to gzip is a work around, although if I had zillions of already deflated blobs this would not really be satisfactory.
[Message sent by forum member 'hanafey' (hanafey)]

http://forums.java.net/jive/thread.jspa?messageID=322367