Make processing hashbang urls an option

[lassombra]

Please make the processing of hashbang urls optional. There are use cases (I have one) where we need to be able to handle those differently.

The case I need is the ability to turn this off because google got into it's results list a large number of incorrect #! endings (where the route is correct, but then ends #!).

Ideally there'd be a configuration option instead to strip the hashbang instead of processing it.

[JNissi]

+1

There should be an option to skip handling the hashbang. I have two different angular applications running under two different iron router routes and I would like to ignore the hashbang completely.

I can reconfigure angular to use '#:' instead of #!, but that isn't optimal as I'm trying to emulate the former url scheme.