Spring MVC RedirectView到带参数的AngularJS URL

Question

I'm trying to redirect my users to an AngularJS style URL:

http://somedomain.com/#/oauth/authorize

And I have some parameters I'm adding to the URL via my model. So far, so standard. Right up until Spring MVC takes a dark and sinister turn inside of RedirectView at line 400. If you click that link you'll see the comment:

// Append anchor fragment, if any, to end of URL.

No! This is not good for AngularJS! That would make my normally beautiful redirect:

http://somedomain.com/#/oauth/authorize?query=params

look like:

http://somedomain.com/?query=params#/oauth/authorize

This is bad juju!

So I have two questions:

1. What purpose does this arrangement of anchor and query params serve.
2. How do I circumvent this devilish machinery?

Thanks for any help!

Answer 1

I feel like I need to take a shower after doing this, but this is a possible solution.

Place this in your main script (ie app.js ) immediately before creating the module in which you configure your $routeProvider .

var urlLoaded = window.location.href;
var qIndex = urlLoaded.indexOf('?');
var hashIndex = urlLoaded.indexOf('#');

if (qIndex !== -1 && hashIndex !== -1 && qIndex < hashIndex) {

    var correctedPath = urlLoaded.substring(hashIndex);
    var correctedParams = urlLoaded.substring(qIndex, hashIndex);
    var base = urlLoaded.substring(0, qIndex);
    var correctedUrl = base + correctedPath + correctedParams;

    window.location.href = correctedUrl;
}

Answer 2

• If you are in the early stages, I would look into using HTML5 pushState. This way you can use anchors like they were meant to be used, and you url's will look cleaner. There are browser limitations to this, and other considerations, but getting it in correctly might save you time down the line from running into this again.

• You can extend this class, override the method, and fix it to be smarter than it currently is. Register it with spring (it might take a couple of overrides, look at ViewControllerRegistry), and if you're feeling nice, submit a Pull Request and see if they want it.

• Beat that URL back into submission in angular as @hartz1989 has suggested

• Instead of doing a redirect, you could respond back with a query parameter that has the redirected url, and add a handler in angular that understands this and does the "redirect". I don't really like this idea, but it is another idea.