If the your encoded query parameters are being unencoded that means you
didn't encode the service url correctly before sending it to CAS.
You need to encode the parameters you need encoded and then encode the
ENTIRE service url as one unit when constructing the login url. That way
when CAS unencodes it to send the redirect your parameters are still
encoded.
Again, CAS is exhibiting the correct behavior. It unencodes the service
parameter as one unit. If you've only partially encoded the service url this
will obviously result in an incorrect unencoding.
-Scott
On Tue, Apr 15, 2008 at 11:15 PM, tom tom <[EMAIL PROTECTED]> wrote:
> Yes I know, but wouldn't it better to keep the encoded
> query parameters(URI) without unencoding?
>
>
> --- Scott Battaglia <[EMAIL PROTECTED]> wrote:
>
> > If it doesn't unencode it then it can't redirect you
> > because the browser
> > wouldn't understand what it was.
> >
> > -Scott
> >
> > On Tue, Apr 15, 2008 at 10:25 PM, Tracy12
> > <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > Hi Scott,
> > > Thanks for the reply, but what my concern is even
> > with fully encoded
> > > service
> > > url, why CAS unencode the service URL when
> > redirecting,
> > >
> > > While am creating the CAS login URL I did fully
> > > encode whatever will be after the "service=". but
> > after the successfull
> > > authentication it unencode and send the URL to the
> > service, Why can't
> > > keep
> > > the same encoded URL and append the ticket towards
> > the end.
> > >
> > >
> > > Pls clarify
> > >
> > > THanks
> > >
> > >
> > > scott_battaglia wrote:
> > > >
> > > > When redirecting back to a service, CAS
> > unencodes the service url,
> > > appends
> > > > a
> > > > ticket and sends it back. When you construct a
> > CAS login url and append
> > > a
> > > > service url to it, you need to encode whatever
> > will be after the
> > > > "service=". Failing to do so will then have CAS
> > unencode whatever part
> > > of
> > > > your URL was encoded for your purposes (since
> > you didn't encode it
> > > before
> > > > handing it to CAS).
> > > >
> > > > -Scott
> > > >
> > > > On Mon, Apr 14, 2008 at 9:23 PM, Tracy12
> > <[EMAIL PROTECTED]> wrote:
> > > >
> > > >>
> > > >> Hi,
> > > >>
> > > >> When CAS redirects the authenticated user back
> > to my application with
> > > the
> > > >> ticket it decode the already encoded URL, What
> > exactly the reason for
> > > >> this,
> > > >>
> > > >> More information.......
> > > >>
> > > >> We have a Apache mod_perl auth handlers, it
> > get fired based on some
> > > URL
> > > >> patterns, when some one try to access the
> > resource (encoded URL) the
> > > >> debug
> > > >> inside the handler clearly shows the encoded
> > URL, then what happens is
> > > it
> > > >> redirect to CAS for Authentication with the
> > encoded URL but after
> > > >> successfull authenthentication, it comes to the
> > same Auth handler, then
> > > >> when
> > > >> I check the URL, it shows the plain URL
> > ignoring all encoding,
> > > >>
> > > >> What is the reason for this, Is there any
> > configuration element for
> > > this.
> > > >>
> > > >> To me it is notihing to do the the Auth
> > Hanlder, but any how for
> > > >> information
> > > >> I use the following to capture the URL and
> > pring
> > > >>
> > > >>
> > > >> my $uri_parsed = $r->parsed_uri;
> > > >>
> > > >> my $unparsed =
> > $uri_parsed->unparse();
> > > >>
> > > >> Apache->warn("value of the unparse is
> > $unparsed");
> > > >>
> > > >> --
> > > >> View this message in context:
> > > >>
> > >
> >
>
> http://www.nabble.com/Why-CAS-behaves-like-this-while-redirecting-tp16693203p16693203.html
> > > >> Sent from the CAS Users mailing list archive at
> > Nabble.com.
> > > >>
> > > >> _______________________________________________
> > > >> Yale CAS mailing list
> > > >> [email protected]
> > > >> http://tp.its.yale.edu/mailman/listinfo/cas
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > -Scott Battaglia
> > > > PGP Public Key Id: 0x383733AA
> > > > LinkedIn:
> > http://www.linkedin.com/in/scottbattaglia
> > > >
> > > > _______________________________________________
> > > > Yale CAS mailing list
> > > > [email protected]
> > > > http://tp.its.yale.edu/mailman/listinfo/cas
> > > >
> > > >
> > >
> > > --
> > > View this message in context:
> > >
> >
>
> http://www.nabble.com/Why-CAS-behaves-like-this-while-redirecting-tp16693203p16715237.html
> > > Sent from the CAS Users mailing list archive at
> > Nabble.com.
> > >
> > > _______________________________________________
> > > Yale CAS mailing list
> > > [email protected]
> > > http://tp.its.yale.edu/mailman/listinfo/cas
> > >
> >
> >
> >
> > --
> > -Scott Battaglia
> > PGP Public Key Id: 0x383733AA
> > LinkedIn: http://www.linkedin.com/in/scottbattaglia
> > > _______________________________________________
> > Yale CAS mailing list
> > [email protected]
> > http://tp.its.yale.edu/mailman/listinfo/cas
> >
>
>
>
>
>
> ____________________________________________________________________________________
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile. Try it now.
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>
--
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
