Hi Tim
Yes, as I described in one of my letters, I have used the
getRequestDispatcher, but when I do, images don't cache
in IE under https, no matter what I am forward'ing to or
include'ing to, whether it is in my web app context
or outside of it. I have a META-INF/context.xml with
allowLinking=
Filters are only run on the incoming request. They can run on include() and
forward() to but you need to see configure that in web.xml.
If you are renaming the servlet path - you can't call chain.doFilter() and
get the results you expect. YOu need to get a new RequestDistpatcher for the
locati
Hello Tomcat users
I am attempting to use a Filter to first modify
a portion of the incoming URL (request.getServletPath())
and next, to send this filtered request on to the
tomcat DefaultServlet. The filter is indeed called
and I am able to complete the first goal of modifying
the incoming URL.
I think this should work in your own web.xml:
MyFilter
default
-Tim
Maurice Yarrow wrote:
Tim
So, my question is: can I request that a filter be applied to all
static page requests that are going to DefaultServlet? Or is this
done with a Valve?
--
Dispatcher(request, response);
rd.forward(request, response);
} else {
filterChain.doFilter(request, response);
}
}
-Tim
Maurice Yarrow wrote:
Hello tomcat users
I have hesitated a while before sending up this question,
for the presumably obvious reason that hacking the tomcat
DefaultSe
this question,
for the presumably obvious reason that hacking the tomcat
DefaultServlet is an act of questionable judgement. But
there are some good reasons why I experimented with this.
In my attempt to get more control over visibility of static
resources on my tomcat 5.0.28, I decided first to
Hello tomcat users
I have hesitated a while before sending up this question,
for the presumably obvious reason that hacking the tomcat
DefaultServlet is an act of questionable judgement. But
there are some good reasons why I experimented with this.
In my attempt to get more control over
