Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You could make it ignore the content type that the JSP page sets. Would that be good enough?<br> How are you doing the plumbing?</p> <p>The basic idea would be to implement a ServletResponseWrapper, override the call to setContentType, and then use a filter to pass this response to the JSP rather than the real one.</p> <p>ResponseWrapperToIgnoreContentType.java</p> <pre><code>import javax.servlet.ServletResponse; import javax.servlet.ServletResponseWrapper; public class ResponseWrapperToIgnoreContentType extends ServletResponseWrapper{ public ResponseWrapperToIgnoreContentType(final ServletResponse response) { super(response); } @Override public void setContentType(final String type) { System.out.println("Ignoring call to set the content type to : " + type); } } </code></pre> <p>Filter to apply it:</p> <pre><code>import java.io.IOException; import javax.servlet.Filter; import javax.servlet.FilterChain; import javax.servlet.FilterConfig; import javax.servlet.ServletException; import javax.servlet.ServletRequest; import javax.servlet.ServletResponse; public class ResponseContentTypeFilter implements Filter{ @Override public void destroy() { } @Override public void doFilter(final ServletRequest request, final ServletResponse response, final FilterChain chain) throws IOException, ServletException { chain.doFilter(request, new ResponseWrapperToIgnoreContentType(response)); } @Override public void init(final FilterConfig filterConfig) throws ServletException { } } </code></pre> <hr> <p>EDIT: Just spotted a flaw in my logic. The content type is required to be set before you can call response.getWriter(), so that it can use the right character encoding. Dunno if this would affect you or not. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload