Okay, here's the bug:
org.apache.coyote.http11.Http11AprProcessor:1504:
response.getContentLengthLong() returns 4, instead of the true file
size, making it appear lower than the minimum compression threshold.
Alex Epshteyn wrote:
>
> Turned out it was the file size. If I arbitrarily t
Turned out it was the file size. If I arbitrarily trim the file to be just
under 50 KB the compression will work.
Looks like the Connector's compression facility is checking for an upper
limit on stream length or something like that.
Does anyone know of a way to disable this upper bound?
Tha
I finally had some time to try to track down this problem further. I set the
log levels to ALL, but still nothing useful showing up. However, I found a
curious thing in my access log. Consider this snippet:
76.19.64.19 - - [18/Apr/2008:04:29:37 +] "GET /theme.css HTTP/1.1" 200
6360
76.19.6
if you have the time try using debug trace to look at every step to see what
is working
Does anyone know what might be happening here? This is a pretty strange
problem...
Thanks for your time,
Alex
--
View this message in context:
http://www.nabble.com/Large-HTML-file-not-getting-compress
Does anyone know what might be happening here? This is a pretty strange
problem...
Thanks for your time,
Alex
Alex Epshteyn wrote:
>
> I have Tomcat's compression enabled:
>
> maxThreads="200" minSpareThreads="25" maxSpareThreads="75"
>enableLookups="false" r
