org.omnifaces.filter
Class CharacterEncodingFilter

java.lang.Object
  org.omnifaces.filter.HttpFilter
      org.omnifaces.filter.CharacterEncodingFilter

All Implemented Interfaces:

javax.servlet.Filter

public class CharacterEncodingFilter
extends HttpFilter

This filter will set the request body character encoding when not already set by the client. Even though JSF2/Facelets uses by default UTF-8 everywhere, which is the best charset choice these days, JSF2/Facelets might fail to set it to UTF-8 when something else has set it to a different value before JSF2/Facelets gets the chance to set it during the restore view phase. PrimeFaces 3.x for example is known to do that. During ajax requests, it will call ExternalContext.getRequestParameterMap() inside PartialViewContext.isAjaxRequest() right before building/restoring the view, which will implicitly set the request body character encoding to the server-default value, which is not UTF-8 per se.

To get this filter to run, map it as follows in web.xml:

 <filter>
   <filter-name>characterEncodingFilter</filter-name>
   <filter-class>org.omnifaces.filter.CharacterEncodingFilter</filter-class>
 </filter>
 <filter-mapping>
   <filter-name>characterEncodingFilter</filter-name>
   <url-pattern>/*</url-pattern>
 </filter-mapping>
 

As JSF2/Facelets uses by default UTF-8 everywhere, the default charset is also set to UTF-8. When really necessary for some reason, then it can be overridden by specifying the encoding initialization parameter in the <filter> element as follows:

 <init-param>
   <description>
     The character encoding which is to be used to parse the HTTP request body. Defaults to UTF-8.
   </description>
   <param-name>encoding</param-name>
   <param-value>ISO-8859-1</param-value>
 </init-param>
 

Please note that this only affects HTTP POST requests, not HTTP GET requests. For HTTP GET requests, you should be specifying the charset at servletcontainer level (e.g. <Context URIEncoding="UTF-8"> in Tomcat, or <parameter-encoding default-charset="UTF-8"> in Glassfish). Also note that this doesn't affect HTTP responses in any way. For HTTP responses, you should be specifying the charset in <f:view encoding>, which also already defaults to UTF-8 by the way.

Since:

1.2

Author:

Bauke Scholtz

Constructor Summary

CharacterEncodingFilter()

Method Summary

void	doFilter(javax.servlet.http.HttpServletRequest request, javax.servlet.http.HttpServletResponse response, javax.servlet.http.HttpSession session, javax.servlet.FilterChain chain) Perform the filtering job.
void	init() Initializes the filter parameters.

Methods inherited from class org.omnifaces.filter.HttpFilter

destroy, doFilter, getFilterConfig, getInitParameter, getServletContext, init

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

CharacterEncodingFilter

public CharacterEncodingFilter()

Method Detail

init

public void init()
          throws javax.servlet.ServletException

Initializes the filter parameters.

Overrides:

init in class HttpFilter

Throws:

javax.servlet.ServletException - When filter's initialization failed.

doFilter

public void doFilter(javax.servlet.http.HttpServletRequest request,
                     javax.servlet.http.HttpServletResponse response,
                     javax.servlet.http.HttpSession session,
                     javax.servlet.FilterChain chain)
              throws javax.servlet.ServletException,
                     java.io.IOException

Perform the filtering job. Only if the request character encoding has not been set yet, then set it.

Specified by:

doFilter in class HttpFilter

Throws:

javax.servlet.ServletException

java.io.IOException

See Also:

Filter.doFilter(ServletRequest, ServletResponse, FilterChain)