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]
