So, this seems to be an issue in tapestry after all. Can any tapestry gurus explain why tapestry would return gzipped content without setting the Content-Encoding header?
-- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-Problem-on-Google-App-Engine-in-Development-tp5716763p5717000.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
