So we have found identified the problem. As I've found in the documentation, Tapestry from version 5.1 compresses requests/responses and assets using gzip. obviously our websphere has some problem with this. Our solution is to disable this feature via configuration property tapestry.gzip-compression-enabled. This has fixed our problem. But from what I've quickly googled, it seems that Websphere indeed messes up something with HTTP headers and compression: http://fixunix.com/websphere/526204-websphere-seems-decompress-gzipped-requests-but-let-thecontent-encoding.html http://fixunix.com/websphere/526204-websphere-seems-decompress-gzipped-requests-but-let-thecontent-encoding.html Thanks for help anyway.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/Migration-from-Tapestry-5-0-18-to-Tapestry-5-2-6-on-Websphere-6-1-tp4774495p4777654.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
