• Bug
  • Status: Closed
  • Resolution: Fixed
  • drb
  • Reporter: sourceforgetracker
  • September 21, 2009
  • 0
  • Watchers: 0
  • September 22, 2009
  • September 22, 2009


Hi, I am using the cachingfilter with SOAP messages. If I got a SOAP fault it has status code 500 which corresponds to the SOAP specs. The cachingfilter does recognize this as internal server error and responds with its own 500 page. At least it does not just forward the contents of the original http response. I fixed the problem by overriding:

net.sf.ehcache.constructs.web.filter.CachingFilter.doFilter where I simply uncommented this stuff:

    //return on error or redirect code
    int statusCode = pageInfo.getStatusCode();
    if (statusCode != HttpServletResponse.SC_OK) {

I am not sure but I believe this is a bug.

Cheers, Tobias Sourceforge Ticket ID: 2430714 - Opened By: t_rothe - 15 Dec 2008 09:35 UTC


Sourceforge Tracker 2009-09-21


The current trunk of ehcache-web has the code uncommented so I guess the bug got resolved somewhere.

It is in ehcache-web, which is a separate download/maven module in ehcache-1.6.

Greg Comment by: gregluck - 4 Apr 2009 07:55 UTC

Fiona OShea 2009-09-22

Re-opening so that I can properly close out these issues and have correct Resolution status in Jira