This functionality was misplaced in mod_gzip anyway. In Apache 2.x, you do that with content negotiation. Specifically, you need to enable MultiViews with the Options directive and you need to specify your encoding types with the AddEncoding directive.
It depends on the Content-Encoding. RFC 2616 has this to say (amongst other things) about Content-Length: Applications SHOULD use this field to indicate the transfer-length of the message-body, unless this is prohibited by the rules in section 4.4. So we have to figure out what transfer-length is; Section 4.4 (Message Length) says these two things … Read more
The correct usage, as defined in RFC 2616 and actually implemented in the wild, is for the client to send an Accept-Encoding request header (the client may specify multiple encodings). The server may then, and only then, encode the response according to the client’s supported encodings (if the file data is not already stored in … Read more
You should use http headers to indicate a connection can accept gzip encoded data, e.g: HttpUriRequest request = new HttpGet(url); request.addHeader(“Accept-Encoding”, “gzip”); // … httpClient.execute(request); Check response for content encoding: InputStream instream = response.getEntity().getContent(); Header contentEncoding = response.getFirstHeader(“Content-Encoding”); if (contentEncoding != null && contentEncoding.getValue().equalsIgnoreCase(“gzip”)) { instream = new GZIPInputStream(instream); }