Thank you very much, Greg. I am hacking OSCache filter that caches content. The problem is not to cache error pages. I tried to check request attributes and javax.servlet.error.servlet_name is really set to 'action' and I could make use of it. But as I got you right, it's not the right way.
Do someone have any suggestions? Thank you. alex Wednesday, September 25, 2002, 5:46:28 PM, you wrote: GW> Alex, GW> In the current version of the spec - filters only get applied GW> to requests as they enter the container - not after request GW> dispatching and undefined for error pages. GW> In JSR154 (the 2.4 version of the spec), I was able to push GW> through some clarifications on the welcome page mechanism and GW> also extend the new Filter definitions to error pages. GW> In 2.4 you will be able to specify if a filter applies to GW> an normal request, a forward, an include or an error page. GW> But that does not help you now! As it is in 2.3 your GW> filter will be applied to the original request, but not GW> for the implicit forwarding to the error page. GW> My only suggestion is to write an error servlet that collects GW> all the details and then does a META redirect to a URL that GW> encodes the details. The redirected request will pass GW> through your filter and will be able to display the results GW> of your filter. Not very nice I'm afraid! GW> regards -- Best regards, Alex Loubyansky ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
