preserving whatever level of encoding was provided to it in the first place.
From: Scott [mailto:scottt...@gmail.com]
Sent: Wednesday, December 17, 2014 1:12 AM
To: cas-dev@lists.jasig.org
Subject: Re: [cas-dev] dotnetcasclient nested url encoding in querystring
"To authenticate with https://cms/
"To authenticate with https://cms/ they need to have setup their account at
a different site, so they get redirected there with a return url pointing
back to the original site, so
https://account/?ret=https%3a%2f%2fcms%2flogin%3fret%3dsecure%252fresource";
I think this redirect might be a problem.
Regarding my nested encoded urls in the querystring use case referenced
earlier, I found another issue. After making the changes in UrlUtil, I was
redirected back to my account site with the correct url
(https://account/?ret=https%3a%2f%2fcms%2flogin%3fret%3dsecure%252fresource&ticket=ST-Blah
I have an ugly use case where the url redirections get a little deep. If a
user is not logged in and accesses a secured resource at
https://cms/secure/resource, they get redirected to
https://cms/login?ret=secure%2fresource. To authenticate with https://cms/
they need to have setup their acco
