On Thu, Jul 16, 2009 at 00:39, Anthony J.
Biacco<abia...@formatdynamics.com> wrote:
> I'm trying to use mod_deflate to compress data coming out of tomcat
> through mod_jk and need the proper content-length header set for the
> COMPRESSED data, but can't do this because the data is streamed and sent
> after the headers are set, therefore we don't know the compressed
> content-length until after the fact.
> I'd either like to request a option to enable such a feature where I can
> have the compressed data buffered, the headers set, and then the data
> sent.
> I'd be willing to pay someone here a nominal free to do it privately, if
> one so wishes to do it.
Have you tried placing the JkMount directive inside a Location and
using just one argument for JkMount?
<LocationMatch /examples/*>
JkMount ajp13_worker
SetOutputFilter DEFLATE
</LocationMatch>
In my case it works, I get a compressed response.
Here are the relevant response headers:
HTTP/1.1 200 OK
Date: Thu, 16 Jul 2009 16:28:19 GMT
Server: Apache/2.2.11 (Debian) mod_jk/1.2.26 mod_perl/2.0.4 Perl/v5.10.0
Accept-Ranges: bytes
ETag: W/"1127-1245356448000"
Last-Modified: Thu, 18 Jun 2009 20:20:48 GMT
Vary: Accept-Encoding
Content-Encoding: gzip
Transfer-Encoding: chunked
Content-Type: text/html
As the transfer is chunked, there's no Content-Length but the response
is still compressed.
Are you constrained not to use chunked transfer?
Sorin
--
A: Because it reverses the logical flow of conversation.
Q: Why is top-posting frowned upon?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
