I did try to escape it but it interprets it as a slash #. Angular introduces the # symbol itself and I'm unable to change it.
I believe my only way out is to have control the user status in the interface. Since all the data comes through REST webservices protected by Shiro it should be okay, even if someone manually changes this status it would not be able to use the application . I was just wondering if a cleaner solution existed. On Wed, Jun 15, 2016, 7:58 AM scSynergy [via Shiro User] < [email protected]> wrote: > I suspect the problem arises from Shiro interpreting the '#' sign as the > start of a comment, so you might want to try and escape it '\#'. Or maybe > you can use some other character instead of the # sign in your URLs? > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://shiro-user.582556.n2.nabble.com/Shiro-and-hashbang-URLs-tp7581066p7581067.html > To unsubscribe from Shiro and hashbang URLs, click here > <http://shiro-user.582556.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7581066&code=Y29zbWUuYmVuaXRvQGdtYWlsLmNvbXw3NTgxMDY2fDQwNjQ1NzkyMw==> > . > NAML > <http://shiro-user.582556.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://shiro-user.582556.n2.nabble.com/Shiro-and-hashbang-URLs-tp7581066p7581068.html Sent from the Shiro User mailing list archive at Nabble.com.
