> I'm also seeing the loss of #k=v URL parameters.
If you are seeing the loss of the "fragment" or "hash" part of the URI (the part that comes after the #), then this is not a CAS issue. The fragment is not sent to the server, so the server can't include it in any redirect. The fragment is handled by the browser and may my or may not be applied to a redirected URI. You need to either send over the fragment information as a query parameter, or else ensure that the user enters your application at a URI that doesnt require a fragment. http://stackoverflow.com/questions/2286402/url-fragment-and-302-redirects http://www.w3.org/Protocols/HTTP/Fragment/draft-bos-http-redirect-00.txt David Ohsie Software Architect EMC Corporation From: jieryn [mailto:[email protected]] Sent: Wednesday, July 17, 2013 11:56 PM To: [email protected] Subject: Re: [cas-user] CAS server not returning request parameter appended to cas login url Greetings, On Tue, Jul 9, 2013 at 1:02 PM, Jérôme LELEU <[email protected]> wrote: If you want to retrieve the redirect=true parameter when redirecting back to myurl, the redirect=true parameter should be properly encode as part of the service parameter. Something like : .../login?service=myurl%3Fredirect%3Dtrue and your service definition should allow extra parameter. Do you have any suggestions for how to do this when your web application is using standard Spring Security to bridge to CAS (3.5.2) automatically? I'm also seeing the loss of #k=v URL parameters. However, my application doesn't actually do any of the redirect / encoding, Spring Security does it.. Thank you in advance, -Jesse -- 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
smime.p7s
Description: S/MIME cryptographic signature
