Wow that is interesting. Does Spring Security fix this issue? Do you want me to give this a try?
regards Malcolm Edgar On Wed, Jun 3, 2009 at 3:27 AM, Bob Schellink (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/CLK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715598#action_12715598 > ] > > Bob Schellink commented on CLK-557: > ----------------------------------- > > Turns out to be Acegi related. If I comment the filter out things go back to > normal. Will try and figure out what Acegi is doing because it seems to > remove the Content-Encoding header. > > We should probably use Spring security instead as that seems to be the > recommended library? > >> PerformanceFilter applied to JSP pages does not always return gzip response >> header >> ---------------------------------------------------------------------------------- >> >> Key: CLK-557 >> URL: https://issues.apache.org/jira/browse/CLK-557 >> Project: Click >> Issue Type: Bug >> Reporter: Bob Schellink >> Assignee: Bob Schellink >> Priority: Blocker >> >> When including JSP pages it seems there are conditions under which the gzip >> header is not returned to the browser. Thus the raw bytes are displayed. >> More strange is that the issue arise only when the size of the Page exceeds >> a certain threshold. This threshold does not seem to be related to the >> PerformanceFilter Gzip threshold of 384 bytes though. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
