So, the header takes precedence over production mode setting and the tapestry.gzip-compression-enabled?
Is this really the case? -borut 2011/9/12 Steve Eynon <steve.ey...@alienfactory.co.uk> > > http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/ResponseCompressionAnalyzer.html > > Looks like it has been doing since T5.1. > > Steve. > > > On 12 September 2011 21:14, Borut Bolčina <borut.bolc...@gmail.com> wrote: > > Hi, > > > > at the moment the only way to configure T5 response compression is via > > tapestry.gzip-compression-enabled. > > > > Should the configuration extend to support checking Accept-Encoding > request > > header? > > > > -borut > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
