Steve Appling a écrit :
Currently the option for compression="on" in the coyote connector is broken
(see bug 18073). The solution presented in the patches attached to that bug
seemed overly complicated. Here is an alternate patch that also fixes the
problem.
This patch changes 3 things:
1) Decreases the minimum compression size to 1k - this seemed to help with
my particular application. There was a lot in the range of 1-2k.
Are you sure you want to compress content less than 2k ?
BTW, you could use compression property for your purpose.
Well, it's a default value. I'd say there's indeed not much point compressing resources which are too small.
2) Checks only that the content type starts with an entry in the
compressableMimeTypes list instead of checking equality. This is the real
bug fix since the contentType also includes the character encoding
information.
That's the way it's done on Apache HTTPD mod_deflate.
But how can it work without the startsWith ? The charset definitely messes up the test. Or we have to look for ";" in the charset String and use a region match.
3) Added application/x-javascript as a default compressable type. Now it
allows all mime types starting with "text/", not just the three previously
specified.
Nope there is problems with many browser which didn't support gzipped javascript.
Sounds reasonable.
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
