[ 
https://issues.apache.org/jira/browse/WW-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17915870#comment-17915870
 ] 

Erica Kane edited comment on WW-5496 at 1/22/25 12:38 AM:
----------------------------------------------------------

I am having the exact same issue and is *not* minor for us; our site is 
completely broken as a result. I am relieved to find this issue as it means we 
aren't the only ones. Our web.xml has the following filter chain:

<filter>
                <filter-name>struts-prepare</filter-name>
                
<filter-class>org.apache.struts2.dispatcher.filter.StrutsPrepareFilter</filter-class>
        </filter>
        <filter-mapping>
                <filter-name>struts-prepare</filter-name>
                <url-pattern>/*</url-pattern>
        </filter-mapping>
                
        <filter>
                <filter-name>sitemesh</filter-name>
                
<filter-class>com.opensymphony.sitemesh.webapp.SiteMeshFilter</filter-class>
        </filter>
        <filter-mapping>
                <filter-name>sitemesh</filter-name>
                <url-pattern>/*</url-pattern>
            <dispatcher>REQUEST</dispatcher>
            <dispatcher>FORWARD</dispatcher>
            <dispatcher>INCLUDE</dispatcher>
        </filter-mapping>

        <filter>
                <filter-name>struts-execute</filter-name>
                
<filter-class>org.apache.struts2.dispatcher.filter.StrutsExecuteFilter</filter-class>
        </filter>
        <filter-mapping>
                <filter-name>struts-execute</filter-name>
                <url-pattern>/*</url-pattern>
        </filter-mapping>

And all the pages come back blank in this configuration.

Please note this is not at all related to the Sitemesh plugin, this is Sitemesh 
2.6.0 which is still under active development and is used by Atlassian, Grails, 
etc. The Sitemesh filter code can be found here:

https://github.com/sitemesh/sitemesh2/blob/2.6.0/src/main/java/com/opensymphony/sitemesh/webapp/SiteMeshFilter.java


 


was (Author: ekane):
I am having the exact same issue and is *not* minor for us; our site is 
completely broken as a result. I am relieved to find this issue as it means we 
aren't the only ones. Our web.xml has the following filter chain:

<filter>
                <filter-name>struts-prepare</filter-name>
                
<filter-class>org.apache.struts2.dispatcher.filter.StrutsPrepareFilter</filter-class>
        </filter>
        <filter-mapping>
                <filter-name>struts-prepare</filter-name>
                <url-pattern>/*</url-pattern>
        </filter-mapping>
                
        <filter>
                <filter-name>sitemesh</filter-name>
                
<filter-class>com.opensymphony.sitemesh.webapp.SiteMeshFilter</filter-class>
        </filter>
        <filter-mapping>
                <filter-name>sitemesh</filter-name>
                <url-pattern>/*</url-pattern>
            <dispatcher>REQUEST</dispatcher>
            <dispatcher>FORWARD</dispatcher>
            <dispatcher>INCLUDE</dispatcher>
        </filter-mapping>

        <filter>
                <filter-name>struts-execute</filter-name>
                
<filter-class>org.apache.struts2.dispatcher.filter.StrutsExecuteFilter</filter-class>
        </filter>
        <filter-mapping>
                <filter-name>struts-execute</filter-name>
                <url-pattern>/*</url-pattern>
        </filter-mapping>

And all the pages come back blank in this configuration.

 

> 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
>            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)

Reply via email to