You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2022. It is now read-only.
I was following to tutorial, and recently I notice the '#' in url path (ex: localhost:4040/#/heroes ) cause quite a lot of troubles.
I'm working on authentication using Microsoft Azure. It asked for the return uri, and if I input the return uri with the '#', error message always pops up. (in my case: http://localhost:8080/#/msauth/ never works, but http://localhost:8080/ works normally.
I open postman, try to add key-value in parameter, and if there is a '#' symbol in the url... it does like this:
You have to provide the PathLocationStrategy instead of the HashLocationStrategy then it will serve without the #, but then you have to handle the non default routes by a server-
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was following to tutorial, and recently I notice the '#' in url path (ex: localhost:4040/#/heroes ) cause quite a lot of troubles.
I'm working on authentication using Microsoft Azure. It asked for the return uri, and if I input the return uri with the '#', error message always pops up. (in my case:
http://localhost:8080/#/msauth/
never works, buthttp://localhost:8080/
works normally.I open postman, try to add key-value in parameter, and if there is a '#' symbol in the url... it does like this:
http://localhost:8080/?param1=value1¶m2=value2#/heroes
The bottom line, I think the '#' is the problem, and it would be nice to get rid of it... I just don't know how.
In order to route, prioritize, and act on this as soon as possible please include:
2.9.2
)MASTER
)The text was updated successfully, but these errors were encountered: