Solution ID 201056033 implemented but changes to signin.html still not seen

Question

Customer have implemented solution id 201056033 in WebLogic 9.2 MP3 patch 2 with PT 8.49.12.
However, when they change signin.html for a web site the change is not seen. Browser cache has been purged.
Yes, the web server were brought down and back up.
Yes, the solution is implemented. It does not work as documented.
Problem being:
Able to change static HTML and have it seen by the user's
browser. The web server is still caching the static HTML page even
though the Solution ID says that doing what is documented in the
solution will solve the problem.
I need an answer to why the Solution ID is not working. I need
to be able to change statuc HTML and have the web server serve it
out to the browser.
weblogic.xml has been updated as solution 201056033, that is to add
'<resource-reload-check-secs>0</resource-reload-check-secs>':
<container-descriptor>
<servlet-reload-check-secs>-1</servlet-reload-check-secs>
<session-monitoring-enabled>true</session-monitoring-enabled>
<resource-reload-check-secs>0</resource-reload-check-secs>
</container-descriptor>
Implemented 201056033 . It does not solve the problem. Why does it not
solve the problem?
Any thoughts , pls help.
Thanks

Answer 1

It's not working because this change only causes the server side to reload the resource. The browser still has it cached, so it ignores it.
What you have to do is send HTTP headers along with the response that convinces the browser not to cache the resource. One way to do this is to implement a servlet filter that injects the appropriate HTTP headers to cause this.
The code for the class could look like this (I haven't declared it in a package, but you should):
import java.io.IOException;
import javax.servlet.Filter;
import javax.servlet.FilterChain;
import javax.servlet.FilterConfig;
import javax.servlet.ServletException;
import javax.servlet.ServletRequest;
import javax.servlet.ServletResponse;
import javax.servlet.http.HttpServletResponse;
public class NoCachingFilter implements Filter
     private FilterConfig filterConfig = null;
     public void destroy()
          this.filterConfig = null;
     public void init(FilterConfig arg0) throws ServletException
          this.filterConfig = filterConfig;
     public void doFilter(ServletRequest request,
                              ServletResponse response,
                              FilterChain chain)
     throws IOException, ServletException
     HttpServletResponse httpResponse = (HttpServletResponse) response;
     httpResponse.setHeader("Cache-Control", "no-cache");
     httpResponse.setDateHeader("Expires", 0);
     httpResponse.setHeader("Pragma", "No-cache");
     chain.doFilter(request, response);
You would declare this filter in your web.xml like this:
<filter>
<filter-name>No Caching Filter</filter-name>
<filter-class>carousel.NoCachingFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>No Caching Filter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
--------------------------