> The protocol mentions that service urls are expected to be encoded, though I > am not sure if CAS attempts to do any sort of decoding of urls internally?
I think the Application server decodes the URL encoded parameters, automatically. There was a discussion a while ago when I worked on the spec regarding wether the URL encoding must be performed or not. As it might be possible that the given service URL holds parameters (e.g. locale), we save us a lot of headache if we expect this parameter as encoded as described currently. Rob Am 18.02.2014 um 22:06 schrieb Misagh Moayyed <[email protected]>: > Team, > It appears that the java CAS client doubly encodes service urls; in > particular the authentication filter. Once when the service url is > constructed (which can be controlled via “encodeServiceUrl”) and then once > when the redirect url to CAS is constructed [1] > > Since service-url encoding is turned on by default, this causes the final url > to be encoded twice. The protocol mentions that service urls are expected to > be encoded, though I am not sure if CAS attempts to do any sort of decoding > of urls internally? > > Might be better to modify the behavior of “encodeServiceUrl” to apply to the > entire redirect url, only once? And CAS to attempt and decode? > > Misagh > > [1] > https://github.com/Jasig/java-cas-client/blob/8742ed6f3747047da3aaf2f60591d3d128193c84/cas-client-core/src/main/java/org/jasig/cas/client/util/CommonUtils.java#L164 > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
