how to decode/encode CAS tickets across HTTP requests ?
Cantor, Scott
cantor.2 at osu.edu
Wed Aug 31 13:15:53 EDT 2016
On 8/31/16, 1:09 PM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:
> > intend to commit a fix and unit test coverage today.
>
> Okay. I encourage use of our (java-supports's) URLBuilder over the
> Spring UriComponentsBuilder, FWIW.
I don't know about URLBuilder, but I just discovered our URLEncoder is not correct if it's used to encode *paths*, though it's ok for query parameters.
We can discuss Friday.
If the CAS ticket is being passed as a parameter, then it really needs to be encoded and decoded. If it's passed as path-info, that would be a different story.
-- Scott
More information about the dev
mailing list