Filters API In Servlets

Introduction

In Servlet applications, a filter can handle security breaches. A filter is a servlet components that provides some useful service to the request and response. The filter lies between the client and the web application. This intercepts the requests to web applications and responses from them. The intercepted requests or responses are manipulated as per the requirements. The request or response manipulation can be checking for the authentication, logging in user information or compressing the data. There can be more than one filter between a client and a web application. This set of filters forms a filter chain. The request and response are processed in each filter of the filter chain sequentially.

How Do Filters Work?

The filter works as an interface between the client and the web application in the following ways,

Intercepts request

The request sent to the web application wrapped in the request object is captured by a wrapper object created by the filters. This wrapped request is then manipulated by the filter.

Processes the wrapped request

The filter then processes the request as per the requirement. The filter contains the method, which actually act over the captured request and modifies the same.

Send request to servlet

Then the modified request is sent to the appropriate servlet wrapped inside a wrapper object.

Processes the wrapped response

The request sent from the servlet, which is already wrapped inside a wrapper object is captured by the filter. The filter then processes the request as per the requirement and generates a response. The processing of the response can dynamically change the format of text sent to the client or compress the amount of data sent to the client over the network.

Sends response

The processed response is then freed by the capture object and captured by the ServletResponse object. Then the response is sent to the client browser.

Filter API

The filter API brings in all the required interfaces for creating a filter class into the javax.servlet package. It contains three interfaces which create and handle the functionalities of a filter. These are Filter interface.FilterConfig interface and FilterChain interface.

Filter Interface

The filter interface is mandatory for creating the filter component in the Web container. Create a class that implements this interface so that it can gain access over the methods in the interface.. Some of the methods in the Filter interface are,

init()

This is called by the servlet container to initialize the filter. It is called once.

public void init(FilterConfig filterConfig)throws ServletException

doFilter()

The doFilter() method of the Filter interface is called by the coordinator each time a request or response is processed.

public void doFilter(ServletRequest req, ServletResponse res, FilterChain chain)throws IOException , ServletException

destroy()

This method is called by the servlet container to inform the filter that its service is no longer required.

public void destroy()

import java.io.IOException;
import javax.servlet.Filter;
import javax.servlet.FilterChain;
import javax.servlet.FilterConfig;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
inport javax.servlet.ServletRequest;
import javax.servlet.ServletResponse;
public class ProcessTimeFilter implements Filter {
private String processingTime = null;
private FilterConfig filterConfig = null;
public void destroy() //destroy() method is called to release the filter from the operation.
{
this.processingTime = null;
this.filterConfig = null;
}
public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
if (processingTime != null) {
request.setAttribute(processingTime, this);
}
//Assign the current time in millisecond to begin.
long begin = System.currentTimrMillis();
chain.doFilter(request, response);
/* The current time in milli seconds after the control passes from one to the next filter is assigned to the variable end.*/
long end = System.currentTimeMillis();
//The processing time is calculated and assigned to the FilterConfig object.
filterConfig.getServletContext().log(this.toString() + ":" + (end - begin) + "milliseconds");
}
//The Filter is initialized
public void init(FilterConfig filterConfig) throws ServletException {
//The filterConfig object is assigned the passed value.
this.filterConfig = filterConfig;
this.processingTime = filterConfig.getInitParameter("processingTime");
}
public String toString() {
if (filterConfig == null) return ("InvokerFilter()");
StringBuffer sb = new StringBuffer("InvokeFilter(");
sb.append(filterConfig);
sb.append(")");
return (sb.toString());
}
}

This code explains a class that extends the Filter interface. This code acts as an interface between a presentation layer application and a servlet. It cannot run without its supporting programs. This calculates the time taken by a servlet to process a request and writes this information to a log file. This uses three methods to carry out the task.

The init() method initializes the filter by configuring the filterConfig object. Then the doFilter() method takes the control. It receives the beginning and end time of the processing of servlet request. Then the total processing time is calculated by the doFilter(). After the processes are over , the next filter in the filter chain is invoked by the chain.doFilter() or the servlet is invoked. After the completion of the filter operation, the destroy() method is invoked , which takes the filter out of memory.

FilterConfig Interface

The FilterConfig interface is vital to initialize the filter. The initialization of filters is done when init() method is called. The init() method retrieves the initial parameters from the FilterConfig object, which is passed to it as argument. It has the following methods.

getFilterName()

This method returns the name of filter defined in the deployment descriptor file web.xml in web application. Syntax : public String getFilterName().

getInitParameter()

This method returns the value of the named initialization parameter as a string.. It returns null if the servlet has no attributes.

Syntax - public String getInitParameter(String name)

getInitParameterNames()

This method returns the names of the initialization parameter as an enumeration of String objects.

Syntax - public Enumeration getInitParameterNames()

getServletContext()

This method returns the ServletContext object used by the caller too interact with its servlet container and filter.

Syntax - public ServletContext getServletContext()

import javax.servlet.FilterConfig;
import javax.servlet.ServletContext;
import java.util.Enumeration;
import java.util.Hashtable;
public class MyFilter implements FilterConfig {
private String name;
private ServletContext servletContext;
private Hashtable initParams;
public MyFilter(String name, ServletContext sc, Hashtable ip) {
name = name;
servletContext = sc;
initParams = ip;
}
public String getFilterName() {
return name;
}
public ServletContext getServletContext() {
return servletContext;
}
public String getInitParameter(String s) {
return (String) initParams.get(s);
}
public Enumeration getInitParameterNames() {
return initParams.keys();
}
}

This source code illustrates the use of the methods in the FilterConfig interface. This program retrieves the initialization parameters using the getInitParameter() method. You can store the parameter names in enumerated variables using the getInitParameterNames() method. The getFilterName() method gets the name of the filter and the getServletContext() method retrieves the ServletContext object.

FilterChain Interface

This interface supports the concepts of filter chain in an application. An object of FilterChain has all the information about the sequence of control flow among a set of filters in a filter chain from the web.xml file. It contains the doFilter (request, response) method, which invokes the next filter in the line of action in a Web application. The below code shows the doFilter(request, response) method is invoked by an object of the FilterChain interface. This is not a standalone program. It needs servlet to run.

public void doFilter(ServletRequest request, ServletResponse response, FilterChain filterChain) throws IOEXception, ServletException {
try {
//This method invokes the next method in the filter chain.
filterChain.doFilter(request, response);
} catch () {
//catch statement
}
}
public void destroy() {
public void init(FilterConfig filterConfig) {}

This source code illustrate that the filterChain object of FilterChain interface is invoking the doFilter(request, response) method.

Conclusion

A filter is a servlet component that provides some useful service to the request and response. A filter works as an interface between the client and the web application and performs intercept requests, processes the wrapped request, sends requests to servlet, and sends responses. The filter API brings in all the required interfaces for creating a filter class into the javax.servlet package. The filter interface is mandatory for creating the filter component in the Web container. The FilterConfig interface is vital to initialize the filter.