Apologies--turns out this not an issue, due to a combination of another developer's and my misunderstanding of URL component hierarchy.
A URL in the form https://client.ucdavis.edu/?ticket=ST-...#/index.html looks to be perfectly valid. Query and fragment components are peer elements, so splitting, validating/discarding the ST, and perhaps recombining what's left (scheme, authority, fragment) is not an incorrect thing to do. Tom. On Aug 7, 2013, at 12:18 PM, Tom Poage <[email protected]> wrote: > Greetings, > > Question on URL encoding the CAS service parameter. > > Platform: CAS 3.5.2 > > Base/protected URL is of the form: > > https://client.ucdavis.edu/#/index.html > > Regular URL encoding into https://cas.../cas/login?service= > > with the service parameter > > https%3A%2F%2Fclient.ucdavis.edu%2F%23%2Findex.html > > returns: > > https://client.ucdavis.edu/?ticket=ST-...#/index.html > > i.e. a literal "#/index.html" tacked on the end. > > Any idea where (and why) this might be failing? > > Tried percent encoding the '#' prior to URL encoding (i.e. double encode the > '#'), but that confused the client server. -- 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-user
