public class FailedRequestFilter extends FilterBase
Note that parameter parsing may consume the body of an HTTP request, so caution is needed if the servlet protected by
this filter uses request.getInputStream() or request.getReader() calls. In general the risk
of breaking a web application by adding this filter is not so high, because parameter parsing does check content type
of the request before consuming the request body.
sm| Constructor and Description |
|---|
FailedRequestFilter() |
| Modifier and Type | Method and Description |
|---|---|
void |
doFilter(ServletRequest request,
ServletResponse response,
FilterChain chain)
The
doFilter method of the Filter is called by the container each time a request/response pair is
passed through the chain due to a client request for a resource at the end of the chain. |
protected Log |
getLogger() |
protected boolean |
isConfigProblemFatal()
Determines if an exception when calling a setter or an unknown configuration attribute triggers the failure of
the this filter which in turn will prevent the web application from starting.
|
initprotected Log getLogger()
getLogger in class FilterBasepublic void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws java.io.IOException, ServletException
javax.servlet.FilterdoFilter method of the Filter is called by the container each time a request/response pair is
passed through the chain due to a client request for a resource at the end of the chain. The FilterChain passed
in to this method allows the Filter to pass on the request and response to the next entity in the chain.
A typical implementation of this method would follow the following pattern:-
1. Examine the request
2. Optionally wrap the request object with a custom implementation to filter content or headers for input
filtering
3. Optionally wrap the response object with a custom implementation to filter content or headers for output
filtering
4. a) Either invoke the next entity in the chain using the FilterChain object
(chain.doFilter()),
4. b) or not pass on the request/response pair to the next entity in the filter chain to block
the request processing
5. Directly set headers on the response after invocation of the next entity in the filter chain.
request - The request to processresponse - The response associated with the requestchain - Provides access to the next filter in the chain for this filter to pass the request and response
to for further processingjava.io.IOException - if an I/O error occurs during this filter's processing of the requestServletException - if the processing fails for any other reasonprotected boolean isConfigProblemFatal()
FilterBaseisConfigProblemFatal in class FilterBasetrue if a problem should trigger the failure of this filter, else falseCopyright © 2000-2024 Apache Software Foundation.
Apache Tomcat, Tomcat, Apache, the Apache Tomcat logo and the Apache logo are either registered trademarks or trademarks of the Apache Software Foundation.