In my angularJS application, I have five routes and dashboard route. After login into my application, dasbhoard is the first route from which all other routes starts. When I am in any one of five routes and hits F5 or browser refresh, my route is changing to default route. Can anyone help me. thanks
Related
I've building a lightweight preact widget that gives users different forms based on current url. I don't want to use preact-router as it would affect the routing of the parent website.
So I went with window.location. But the issue, I'm facing is when users navigate internally from one page to another,unless there is refresh, window.location doesn't update the current URL.
Hence if i want to send form 1 to users at /home and form 2 to users at /settings. Users get the same form for both /home and /settings when users navigate internally and only change when they do a refresh.
Can someone suggest me a lightweight solution to fix this? Does in-memory router works for my use-case?
I'm using ReactJS for my next project and am using JWT and storing it in LocalStorage for persistent login. The issue occurs whenever I refresh my website, the navbar flickers between auth links and guest links. Can anyone help with the flickering/flashing between states while using persistent login?
I am using react router. Assume I am in /dashboard route.
Now if I refresh the page, request will go to the server. And server redirects to /. What happens here is, I am navigated to / route, instead of /dashboard.
What I want is, When I refresh the page, I want to navigate to the same route instead of navigating to /.
Can anyone help me in resolving this issue?
Sorry this is my production server configuration issue
we are redirecting "/" from the server for all get routes instead of sending the "index.html" file.
I developed a react based application and the router is working fine but when i am doing refresh the route which is not rendering same page which goes to error page or login page.
Tried with React router
In my react app I have protected routes such as /admin.
If a user accesses this route who does not have permissions to view the page I replace the route with a /forbidden route.
From the forbidden page the user can press a back button which works fine, if the request came from in app routing.
What can I do if a user accesses this route directly over the browser?
I want the user to return to the start page but currently he gets redirected to my oidc providers page.