Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: error (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <3755326.xmGJNfvh73@caridad>
References: <1920484.F5dMfWpbVD@caridad>
	<4151683.X4RTdSuXFG@caridad>
	<CABLGb9yFvE8pBrjntWYmwMcVf2Ww35CjB+_Yxmfm5w1WpVzaTw@mail.gmail.com>
	<3755326.xmGJNfvh73@caridad>
Date: Fri, 12 Jul 2013 12:33:43 +0100
Message-ID: 
 <CALaBdorsMnyZnjM=3Cd_CH1FZutAF25wO_qxEZSY3iZ+cgEZJQ@mail.gmail.com>
Subject: Re: S2 custom authentication: remembering original request
From: Antonios Gkogkakis <gkogkaka@tcd.ie>
To: Struts Users Mailing List <user@struts.apache.org>
Content-Type: multipart/alternative; boundary=047d7b6705b9129a8704e14ee281

--047d7b6705b9129a8704e14ee281
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

  try
 request.setAttribute("url",invocation.getInvocationContext().getName()) in
your interceptor.

Antonios


On 12 July 2013 12:03, Antonio S=E1nchez <juntandolineas@gmail.com> wrote:

> I'm having problems with chaining. I have tried several ways but none
> works. For instance:
>
> 1. http://localhost/mycontext/secure/protected =3D> Login.jsp
> (${#request.url} is readable in jsp).
>
> 2. Login.jsp =3D> submit (correct user/pwd) =3D> ERROR: Infinite recursio=
n
> detected: [//authenticate!authenticate, //, //] (url not available as
> request attribute)
>
> When submitting, request attribute 'url' is not present in the action, I
> guess because result type of "input" is "dispatcher", not "chain", but
> using type "chain" with a JSP causes St2 to complain, and won't find any
> action.
>
> Pseudo-code:
>
> INTERCEPTOR
>         if (userInSession =3D=3D null) {
>             request.setAttribute("url", request.getServletPath());
>             return "AUTHENTICATE";
>         }
>
>         return invocation.invoke();
>
> STRUTS.XML
>
>  - package base, namespace ""
>         - defines interceptor SECURE and default interceptor stack
> (SECURE, DEFAULTSTACK).
>         - defines global result:
>             <result name=3D"AUTHENTICATE" type=3D"chain">
>                 <param name=3D"actionName">authenticate</param>
>                 <param name=3D"namespace">/</param>
>             </result>
>
>  - package root extends base, namespace "/"
>         <action name=3D"authenticate" class...>
>             <result type=3D"chain">
>                 <param name=3D"actionName">${#request.url}</param>
>             </result>
>             <result name=3D"input">/Login.jsp</result>
>         </action>
>
>  - package secure extends base, namespace "/secure"
>         <action name=3D"protected" class=3D...>
>             <result>/secure/Protected.jsp</result>
>         </action>
>
> ACTION AUTHENTICATE
>
>         if (userInSession !=3D null ) {
>                 request.getSession().setAttribute("USER_IN_SESSION",
> userInSession);
>                 //expecting original url is a request attribute
>                 return SUCCESS;
>         } else {
>             return INPUT;
>         }
>
> At the moment I've not been able to implement the requirement.
>
>
> El Mi=E9rcoles, 10 de julio de 2013 10:07:36 Paul Benedict escribi=F3:
> > Forwarding to another action means you want to do chaining:
> > http://struts.apache.org/release/2.3.x/docs/action-chaining.html
> >
> > <result type=3D"chain">
> >     <param name=3D"actionName">autenticar</param>
> > </result>
> >
> >
> > On Wed, Jul 10, 2013 at 10:00 AM, Antonio S=E1nchez
> > <juntandolineas@gmail.com>wrote:
> >
> > > Can't forward even without using global results:
> > >
> > >  http://localhost:8084/mycontext/autenticar =3D> login.jsp - OK
> > >
> > >         <action name=3D"forward">
> > >             <result>/autenticar</result>
> > >         </action>
> > >
> > > http://localhost:8084/mycontext/forward =3D> 404 ERROR -
> > > /mycontext/autenticar not available
> > >
> > > Which is the right way to forward to actions?
> > >
> > > Using 2.3.15.
> > >
> > > El Mi=E9rcoles, 10 de julio de 2013 15:29:51 usted escribi=F3:
> > > > > Second question: because it's a redirect, hence a new request.
> > > >
> > > > http://localhost:8084/mycontext/autenticar =3D> login.jsp - OK
> > > >
> > > > Returned by interceptor:
> > > >
> > > >         <global-results>
> > > >             <result name=3D"AUTENTICAR">/autenticar</result>
> > > >         </global-results>
> > > >
> > > > http://localhost:8084/mycontext/admin/protected =3D> 404 ERROR -
> > > /mycontext/autenticar not available
> > > >
> > > > How should I "forward" to actions?
> > > >
> > > >
> > > >
> > > > El Mi=E9rcoles, 10 de julio de 2013 07:43:38 Dave Newton escribi=F3=
:
> > > > > Second question: because it's a redirect, hence a new request.
> > > > >
> > > > > Dave
> > > > >  On Jul 10, 2013 7:28 AM, "Antonio S=E1nchez" <
> juntandolineas@gmail.com>
> > > > >
> > > > > wrote:
> > > > > > Use Case: request some protected resource -> redirect action fo=
r
> > > > > > authentication -> access protected resource.
> > > > > >
> > > > > > I'm using a custom interceptor that redirects (redirectAction)
> to a
> > > global
> > > > > > result if no user object is found in session. The final action
> > > result then
> > > > > > redirects to a login page.
> > > > > >
> > > > > > The interceptor gets the original action requested (using
> > > > > > request.getServletPath(), but not sure if this is right), and
> puts
> > > it in
> > > > > > the value stack. It would be used with dynamic redirection in t=
he
> > > final
> > > > > > result upon login success( ${nextAction} ) . This action must b=
e
> > > passed in
> > > > > > between redirections.
> > > > > >
> > > > > > But I need to reuse the original request. Reconstructing the
> request
> > > with
> > > > > > a query string is not an option. I need the original request:
> > > GET/POST
> > > > > > method, all parameters/values, maybe uploading binary content
> > > > > > (inputstream), maybe headers...
> > > > > >
> > > > > > Is it possible to do this? How?
> > > > > >
> > > > > > ------
> > > > > >
> > > > > > Partially related to this: I'm having problems with
> redirections. The
> > > > > > original request parameters are forwarded only using dispatcher
> > > result .
> > > > > > If
> > > > > > I use redirectAction or redirect, original params are lost. Why=
?
> > > > > >
> > > > > >
> ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > > > > > For additional commands, e-mail: user-help@struts.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: user-help@struts.apache.org
> > >
> > >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
>

--047d7b6705b9129a8704e14ee281--