Hi Peter,
Peter Crowther wrote:
There was a similar thread a couple of months back. The conclusion of
that thread was that you cannot clone the original or create a new
request, and that there are sound architectural reasons for this.
Instead, you'll have to do it the proper way - store
Hi Mark,
Take a look at how form authenticator does it. See
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/authenticator/FormAuthenticator.java?rev=1.24view=markup
and the SavedRequest class in the same package.
Note that the way this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
this is my first mail to this list, forgive me for any mistake I may make...
I'm developing a authorization filter for Tomcat 5; in some cases, if
the user credentials are invalid, I have to save the original request,
redirect the user
From: Ajay Arjandas Daryanani [mailto:[EMAIL PROTECTED]
I'm developing a authorization filter for Tomcat 5; in some cases, if
the user credentials are invalid, I have to save the original request,
redirect the user to an external authentication engine, handle the
response and then proceed
Take a look at how form authenticator does it. See
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/authenticator/FormAuthenticator.java?rev=1.24view=markup
and the SavedRequest class in the same package.
Note that the way this restores the
