okay

i would try to replace the redirect-to
by a generate with the cocoon://

because redirect-to seems not to be an internal redirect but an external
one.


----- Original Message -----
From: "andi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 09, 2003 4:24 PM
Subject: Re: problem with redirect-to and WAP-browser


>
> --- Bruno PIERRE <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > you mustn't use server-side redirect for wap because
> > some gateway and/or
> > phone does not support it.
> > with cocoon you can use the cocon:// to generate the
> > page instead of a
> > redirect to it.
> >
> > or try client-side redirect, it works.
> >
> > Bruno
>
> Alright, but it seems to me that the
> DefaultAuthenticationmanager doesn't use the cocoon://
> rightly because it always calls globalRedirect(). Am I
> wrong here?
>
> Even if I use the cocoon:// protocol in the
> authentication-manager redirect-to , i see the
> forwarded address in the log of my WAP-Gateway, which
> shouldn't be the case with the cocoon "internal
> redirect"
>
> thanks for your help.
>
> andi
>
> >
> > ----- Original Message -----
> > From: "andi" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, July 09, 2003 1:08 PM
> > Subject: problem with redirect-to and WAP-browser
> >
> >
> > > Hi there,
> > >
> > > I've got a problem with redirect-to in the
> > > authentication-framework using a strict
> > WAP-browser
> > > (Nokia6210 simulator). browser reports: unknown
> > > content-type
> > >
> > > i use cocoon 2.1m2 in jetty on win NT
> > >
> > > i think it is because of the content-type of the
> > > redirect. My auth-configuration is:
> > >
> > >             <authentication-manager>
> > >                 <handlers>
> > >                     <handler name="mHandler">
> > >                         <map:redirect-to
> > > uri="cocoon:/loginpage" />
> > >                         <authentication
> > > uri="cocoon:/authenticateUser" />
> > >                     </handler>
> > >                     .
> > >                     .
> > >
> > > i tried without the cocoon-protocol, which does
> > not
> > > make any difference..
> > >
> > > i digged abit in the code.
> > > is it intentional that the authentication-fw
> > always
> > > uses the globalRedirect-method.
> > > (redirector.globalRedirect(false,
> > > SourceUtil.appendParameters(redirectURI,
> > > parameters));)
> > >
> > > (for those who are interested in
> > redirectionproblems
> > > in wap read this thread:
> > >
> >
> http://groups.yahoo.com/group/wmlprogramming/message/7812
> > > )
> > >
> > > does anyone know a solution.
> > >
> > > TIA.
> > >
> > > andi
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > SBC Yahoo! DSL - Now only $29.95 per month!
> > > http://sbc.yahoo.com
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> >
>
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to