I thought about trying without APR, but wasn't sure how to disable it (on
Linux).
Anyways, I've worked around this problem by implementing my own filter that
serves up a pre-gzipped version of the files that aren't getting compressed.
Alex
Caldarale, Charles R wrote:
&
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
bound?
Thanks,
Alex
Alex Epshteyn wrote:
>
> 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 -
3) filename too long.
That's pretty much it. I don't think it's the contents inside the file -
I've gone through several incarnations of these (they are generated by my
compiler), and not a single one has successfully gotten gzipped.
Thanks again for your time,
Alex
Alex Epsh
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="
Say I have the following filter which is responsible for timing all requests
in my application:
public void doFilter(ServletRequest request, ServletResponse response,
FilterChain filterChain) throws IOException, ServletException {
startTiming(request, response);
filterChain.doFilter(reque
case-insensitive file systems like *FAT and NTFS).
On Sun, Mar 30, 2008 at 4:01 PM, Alex Epshteyn
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> Suppose I have the following in my server.xml:
>
>autoDeploy="true" xmlValidation="false" xmlNamespaceAware="fa
I have Tomcat's compression enabled:
It works as expected for all my resources (stylesheets, scripts, etc)
except for one static file, which has the extension .cache.html (in
case you're wondering, it contains scripts generated by GWT). This
file is pretty large - about 150K, but Tomcat doesn't
Hi,
Suppose I have the following in my server.xml:
This causes Tomcat to deploy two instances of the "foo" webapp - one
as path "/foo/" and one as "/". I only want one instance deployed at
"/". Any ideas?
This is the only strategy I've found for replacing the ROOT app with
my ow
