Tracking Issue: Auto Compression can cause regressions
------------------------------------------------------
Key: TAP5-445
URL: https://issues.apache.org/jira/browse/TAP5-445
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.1.0.0
Reporter: Fernando
I have to report a huge regression because of Tapestry Compression.
I just tried running with the latest tapestry and it worked just fine most of
the time ( going against browsers ), but we interact with the Facebook proxy,
and it looks like they got totally confused with the tapestry compression
support, thus they would only serve up an error page. Luckily, with Tapestry's
new configuration override feature (thank you howard), I was able to turn it
off easily, and have my app working again.
public void contributeHttpServletRequestHandler(
OrderedConfiguration<HttpServletRequestFilter> configuration ) {
configuration.override( "GZIP", null );
}
So I wanted to report this regression, it might be the case that I'm the only
one affected, but we don't for sure, and probably people will never realize why
it doesn't work. I don't know if any other issues might arise from
tapestry-compression, but I will want to make sure I can turn the feature off
as I need to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
