In your struts.xml add: <constant name=”struts.action.excludePattern” value=”/ServletToExcludeFromStruts*”/> The value be comma delimited as well for multiple exclusions. See http://struts.apache.org/2.2.1/docs/webxml.html
The complicated way to achieve my goal was indeed to write my own javax.servlet.Filter and to embed it into the filter chain. This solution complies with the Apache Tomcat suggestion provided in Tomcat Wiki – Character Encoding Issues. Update (2010-07-31): The first version of this filter interpreted the query string itself, which was a bad … Read more
BalusC’s answer is good, but it might be a little overwhelming if you’re just starting out. Put simply: SerlvetResponse and its extension, HttpServletResponse, are interfaces telling you what methods are available to call to do the things you need. In the normal course of working with Filters, Servlets, et al., you’ll use HttpServletResponse often to … Read more
When using Spring Boot As mentioned in the reference documentation, the only step needed is to declare that filter as a Bean in a configuration class, that’s it! @Configuration public class WebConfig { @Bean public Filter shallowEtagHeaderFilter() { return new ShallowEtagHeaderFilter(); } } When using Spring MVC You’re probably already extending a WebApplicationInitializer. If not, … Read more
The filter chain in essence wraps the servlet invocation. The chain will process all links until it hits the “bottom”, then allow the servlet to run, and then return up the chain in reverse. For example, if you have a new “example filter”, your doFilter() method may look like this: public void doFilter(ServletRequest request, ServletResponse … Read more
The javax.servlet dependency is missing in your pom.xml. Add the following to the dependencies-Node: <dependency> <groupId>javax.servlet</groupId> <artifactId>javax.servlet-api</artifactId> <version>3.0.1</version> <scope>provided</scope> </dependency>
String sql=”select * from reg where username=””+user+”” and pass=””+pwd+”””; This is an extremely bad practice. This approach requires that both username and password being passed around plain vanilla through requests. Moreover, you’ve there a SQL injection attack hole. Make use of sessions, in JSP/Servlet there you have the HttpSession for. There is really also no … Read more
No, you can’t use a regex there. According to the Java Servlet Specification v2.4 (section srv.11.1), the url-path is interpreted as follows: A string beginning with a ‘/’ character and ending with a ‘/*’ suffix is used for path mapping. A string beginning with a ‘*.’ prefix is used as an extension mapping. A string … Read more
In order to get HttpServletRequest#getParts() to work in a Filter in Tomcat, you need to set allowCasualMultipartParsing=”true” in the webapp’s <Context> element in Webapp/META-INF/context.xml or Tomcat/conf/server.xml. <Context … allowCasualMultipartParsing=”true”> Because as per the servlet 3.0 specification the HttpServletRequest#getParts() should only be available inside a HttpServlet with the @MultipartConfig annotation. See also the documentation of the … Read more
After couple of hours of struggling, I’ve finally found the solution. In short, ContentCachingResponseWrapper.copyBodyToResponse() should be called in the end of the filter method. ContentCachingResponseWrapper caches the response body by reading it from response output stream. So, the stream becomes empty. To write response back to the output stream ContentCachingResponseWrapper.copyBodyToResponse() should be used.