All Open JIRA issues are now moved to Github, and tracked under Github Issues. The migration is now complete. Please use Github issue tracking to file and track issues. JIRA issues will be closed.
I wonder if this could be done via a configuration option (regex) to support a flexible solution?
ScottSAugust 9, 2013 at 3:11 AM
Is the /#/ pattern the pattern that most of these client side frameworks use? If so we can attempt to account for that in the redirect logic. I really don't like one-off solutions because clients want to do wonky things but I've seen this pattern gain enough momentum.
ScottSAugust 9, 2013 at 3:09 AM
Lowering severity as CAS is generating correct URLs. It would be nice to support AngularJS (or whatever you are using) though supporting this would probably also require changes to the CAS Client since anything after # would not be considered part of the query string.
It looks like as if changed the "redirect url" composition. Our application URLs look like:
http://someurl.com/#/index.html
The "#/" is used by the client side framework's routing functionality. The expected redirect URL should be:
http://someurl.com/#/index.html?ticket=<ticket>
..., however the current CAS version generates:
http://someurl/?ticket=<ticket>#/index.html