I'm fine with dealing with it as is. I just think it's funny that I never had any GZip issues until I moved to using EhCache's GZipFilter. When I used my own, it worked great. Oh well, that's the nature of OS and trying to integrate so many things together.
Matt Jessek wrote: > > Ah yes it is in fact doing some gzip filtering already. I think by > default Tapestry will only do this to tapestry framework related > resources but it's only a couple lines of hivemodule.xml configuration > to make it do it to "everything". > > (or perhaps I should allow for an option to disable it, or even > better would be ehcache looking at content-encoding and deciding to > not re-encode it again if already encoded but ehh....) > > It should be fairly easy for me to make it a configurable option to > disable if you like either way. (though I think anyone trying to do > gzip / other kinds of things to web apps these days will probably > start to think about the possibility that it's already been done for > them more and more as this "out of the box" feature becomes more > popular) > > On 8/22/07, mraible <[EMAIL PROTECTED]> wrote: >> >> This appears to be caused by EhCache's GZipFilter (v 1.3.0). This is >> strange >> since the rest of my .js files work fine with this filter. >> >> Here's the response headers with the gzipFilter enabled: >> >> Expires: Thu, 21 Aug 2008 23:33:06 GMT >> Last-Modified: Wed, 22 Aug 2007 23:13:32 GMT >> Cache-Control: public, max-age=7776000 >> Content-Encoding: gzip >> Etag: W/"36171-1187824412000" >> Content-Length: 36204 >> Content-Type: application/x-javascript; charset=UTF-8 >> Server: Jetty(6.1.5) >> >> 200 OK >> >> And without: >> >> Expires: Thu, 21 Aug 2008 23:36:54 GMT >> Last-Modified: Wed, 22 Aug 2007 23:13:32 GMT >> Cache-Control: public, max-age=7776000 >> Content-Encoding: gzip >> Etag: W/"36171-1187824412000" >> Content-Length: 36171 >> Content-Type: application/x-javascript; charset=UTF-8 >> Server: Jetty(6.1.5) >> >> 200 OK >> >> Is Tapestry already doing some gzipping? It looks like the file is >> smaller >> w/o the EhCache filter enabled. >> >> Thanks, >> >> Matt >> >> >> mraible wrote: >> > >> > I tried backing down to 4.1.2 and my application at least comes up. I >> > noticed it's now including a dojo javascript file. However, if I >> navigate >> > to its path: >> > >> > http://localhost:9000/assets/static/dojo-0.4.3/dojo3.js >> > >> > It's all jumbled text with funky characters instead of JavaScript. Is >> this >> > as designed? >> > >> > Matt >> > >> > <sample> >> > � >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Problems-with-tapestry-spring-while-upgrading-from-4.1.2-SNAPSHOT-to-4.1.3-SNAPSHOT-tf4275060.html#a12285008 >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Jesse Kuhnert > Tapestry/Dojo team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > > -- View this message in context: http://www.nabble.com/Problems-with-tapestry-spring-while-upgrading-from-4.1.2-SNAPSHOT-to-4.1.3-SNAPSHOT-tf4275060.html#a12741474 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
