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

Reply via email to