I like that I can just apply my filter to any application without changing
anything in the application itself.
Anders
-Ursprungligt meddelande-
Frn: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Fr Marcel Schutte
Skickat: den 23 mars 2001 14:42
Till: Orion-Interest
mne: Re: Problem with
Hello,
I am trying to use filters for authenticating users. My filter uses
RequestDispatcher.forward to show a login page when the user needs to
authenticate himself.
This results in the filter beeing invoked again. It seems that the
RequestDispatcher in orion (both forward and include) invokes
Title: SV: Problem with Filters and RequestDispatcher in Orion 1.4.5
My
filter and it's mapping is shown below. Tomcat does not invoke the filter when
the RequestDispatcher is used.
Since
the RequestDispatcher is internal it would seem that it should not invoke the
filters. This is however
Title: SV: Problem with Filters and RequestDispatcher in Orion 1.4.5
Orion
invokes filters on _every request_. That's internal and external. This is IMHO
the way it should be done. (Some filters require this to work!) Tomcat only
invokes it on _external requests_. AFAIK there is some debate
Title: SV: Problem with Filters and RequestDispatcher in Orion 1.4.5
Orion
invokes Fitlers on any request, which is the way it should work
IMHO.
And
yes, you need to move your loginPage and failedLoginPage out of the /html/* in
order for the filter not to be invoked when opening those
Just out of curiosity, but why don't you use the standard servlet provisions
for authentication? Are there things you can do more easily using filters?
I'm just starting to look at what filters can do, so any comments are
welcome.
Marcel
- Original Message -
From: "Anders Janmyr" [EMAIL
