"gzip" is the gzip format, and "deflate" is the zlib format. They should probably have called the second one "zlib" instead to avoid confusion with the raw deflate compressed data format. While the HTTP 1.1 RFC 2616 correctly points to the zlib specification in RFC 1950 for the "deflate" transfer encoding, there have been reports of servers and browsers that incorrectly produce or expect raw deflate data per the deflate specficiation in RFC 1951, most notably Microsoft. So even though the "deflate" transfer encoding using the zlib format would be the more efficient approach (and in fact exactly what the zlib format was designed for), using the "gzip" transfer encoding is probably more reliable due to an unfortunate choice of name on the part of the HTTP 1.1 authors.

require IO::Uncompress::Inflate;

my $output;

my $status = IO::Uncompress::Inflate::inflate($content_ref, \$output, Transparent => 0);

my $error = $IO::Uncompress::Inflate::InflateError;

unless ($status) {

# "Content-Encoding: deflate" is supposed to mean the

# "zlib" format of RFC 1950, but Microsoft got that

# wrong, so some servers sends the raw compressed

# "deflate" data. This tries to inflate this format.

$output = undef;

require IO::Uncompress::RawInflate;

unless (IO::Uncompress::RawInflate::rawinflate($content_ref, \$output)) {

$self->push_header("Client-Warning" =>

"Could not raw inflate content: $IO::Uncompress::RawInflate::RawInflateError");

$output = undef;

}

}

The deflate encoding is not supported, please check the zlib's documentation for a complete explanation.