Some problems with route authorization
See original GitHub issueClone above repo
npm i
npm run build
cd api
npm i
cd ..
swa start dist --api api
Go to http://localhost:4280
and log in.
/.auth/me
verifies logged in
/
still returning 401/api/info
still returning 401
CLI v0.3.0
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (11 by maintainers)
Top Results From Across the Web
Protected Routes and Authentication with React Router - ui.dev
Protected routes let us choose which routes users can visit based on whether they are logged in.
Read more >React Router Authorization - Stack Overflow
"Called when a route is about to be entered. It provides the next router state and a function to redirect to another path....
Read more >Complete guide to authentication with React Router v6
Learn how to handle user authentication with React Router v6 and gain a better overall understanding of how React Router works.
Read more >Implementing Protected Route and Authentication in React-JS
For this tutorial, I'll be showing how to set up an authentication route and protect other routes from been accessed by unauthorized users....
Read more >The New Way To Create Protected Routes With React Router V6
Updated version of how to create protected routes in react router v6.Check out the article that goes with this: ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@manekinekko Thanks! I’m looking forward to the release of next version.
@manekinekko This didn’t seem to fix the issue for me. Can you try cloning the repo and see if you can reproduce with the latest build from main?