I believe so. I read the documentation too, which list these requirements. I also looked at the source for the gzip filter on this version of jetty. It appears that the 0 Default might be wrong but that does not matter in this case. I created files that would match all of the above as best I could.
I turned on detail logging and I can see the gzip filter in the chain but the files never seem to be gzipped. I will try setting up a public test if I have time later today. Has anyone else got gzip to work on Jetty 9.2.x? Box is - Windows 7 Pro 64 bit. - Java is 1.8_20 - Jetty 9.2.6 - client is Chrome. Will try creating a better test too. Andy On Mon, Jan 12, 2015 at 8:29 AM, Stefan Magnus Landrø < [email protected]> wrote: > Have you verified all this? > > GZIP Filter This filter will gzip or deflate the content of a response if: > > - The filter is mapped to a matching path > - accept-encoding header is set to either gzip, deflate or a > combination of those > - The response status code is >=200 and <300 > - The content length is unknown or more than the minGzipSize > initParameter or the minGzipSize is 0(default) > - If a list of mimeTypes is set by the mimeTypes init parameter, then > the Content-Type is in the list. > - If no mimeType list is set, then the content-type is not in the list > defined by excludedMimeTypes > - No content-encoding is specified by the resource > > > > > 2015-01-12 12:32 GMT+01:00 Andrew Penhorwood <[email protected]>: > >> I am using chrome and I can see the gzip accept headers in the request. >> I can also see that the file size never changes when it comes across the >> wire. >> >> >> On Mon, Jan 12, 2015 at 2:15 AM, Christoph Läubrich < >> [email protected]> wrote: >> >>> Gzip must be requested by the client, have you checked that the client >>> actually request compressed data? What client do you use? >>> Also make sure your files have proper mime types and try to enable only >>> for a specific mime type to test. >>> >>> Beside this: How do you verify that content is Gzipped? Some versions of >>> IE+Firebug Console do not report the gzip content type. So you should >>> actually check with wire-shark or a simple java test client (just make sure >>> to request compression!) >>> >>> Am 11.01.2015 20:14, schrieb Andrew Penhorwood: >>> >>>> I am using jetty9.2.6. The site has ran for months without issue on >>>> the Jetty 9.2.x codes bases. I decided to audit the site to see if there >>>> were things we could do to make it more efficient. One of those things was >>>> enabling gzip. So I added the gzip filter to to my webdefault.xml file. >>>> >>>> >>> _______________________________________________ >>> jetty-users mailing list >>> [email protected] >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >>> >> >> >> >> -- >> Andrew Penhorwood >> [email protected] >> www.coldbits.com >> >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > -- > BEKK Open > http://open.bekk.no > > TesTcl - a unit test framework for iRules > http://testcl.com > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- Andrew Penhorwood [email protected] www.coldbits.com
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
