views:

43

answers:

1

What InputStream type should be used to handle URLConnection streams that have HTTP Content-Encoding set to deflate?

For a Content-Encoding of gzip or zip I use a GZIPInputStream, no problem.

For a Content-Encoding of "deflate" I have tried using InflaterInputStream and DeflaterInputStream but I get

java.util.zip.ZipException: unknown compression method at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:147)

My understanding is that "deflate" encoding refers to Zlib compression, and according to the docs this should be handled by InflaterInputStream.

+1  A: 

In HTTP/1.1, Content-encoding: deflate actually refers to the DEFLATE compression algorithm, as defined by RFC 1951, wrapped in the zlib data format, as defined by RFC 1950.

However some vendors just implement the DEFLATE algorithm as defined RFC 1951, completely ignoring RFC 1950 (no zlib headers).

Others have been hit by the same issue:

In order to work around this, try to instantiate the InflaterInputStream passing an Inflater that was created with the nowrap parameter set to true:

in = new InflaterInputStream(conn.getInputStream()), new Inflater(true));
Grodriguez
Both RFCs seem to reference Zlib, but I guess different versions?
Joel
"6.2.2.2 Deflate CodingThe "deflate" format is defined as the "deflate" compression mechanism (described in [RFC1951]) used inside the "zlib" data format ([RFC1950]).Note: Some incorrect implementations send the "deflate" compressed data without the zlib wrapper." -- http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-11.html#rfc.section.6.2.2.2
Julian Reschke
Your suggestion to pass the Inflater worked! Thanks.
Joel