[
https://issues.apache.org/jira/browse/WW-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916780#comment-17916780
]
Erica Kane commented on WW-5496:
--------------------------------
Tomcat 11 is not stable. See [Apache Tomcat: Which version do I
want?|https://tomcat.apache.org/whichversion.html] and scroll to the bottom of
the page.
Obviously we also will need this issue fixed before we are required to move to
Tomcat 11, but I expect that will be a while. We would not run an alpha release
in production. I suspect it has to do with filter chaining in some way, perhaps
some difference between Servlet 6.0 and 6.1.
> Struts filter and HttpServletResponseWrapper
> --------------------------------------------
>
> Key: WW-5496
> URL: https://issues.apache.org/jira/browse/WW-5496
> Project: Struts 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.0.0
> Environment: Tomcat 11
> Reporter: Günter Paul
> Priority: Minor
> Fix For: 7.1.0
>
>
> I've been using a servlet filter for a long time. It removes spaces in the
> lines (trim()) and line breaks (only for *.action requests).
> The filter is installed in the web.xml before the struts filter. It works
> very well so far, even with the current Struts 7.0.0-M10 version.
> Until now I was using Tomcat 10. After switching to Tomcat 11, only blank
> pages are displayed.
> If I use a web-application without struts, the filter works fine. Only when
> the Struts filter (StrutsPrepareAndExecuteFilter) is installed does the
> output of the wrapper appear to no longer be included in the output stream.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
