Callback url causes 404 page to be displayed
See original GitHub issueIn the documentation, it is stated
You still need to setup a redirect uri, which must point to your application, but you do not need to create that route.
I found this misleading because in the common case of using react-router-dom@6
with a 404 catch-all route, the 404 page is displayed when the code exchange callback route is navigated to.
Should we not encourage the user to set up a route like so?
<Route path={ROUTES.CALLBACK} element={<LoadingIndicator />} />
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Error 404: 4 Ways to Fix It - Hostinger
Error 404 is a response code, meaning the server could not locate the requested content. Check this article to learn 4 steps to...
Read more >How To Find & Fix 404 Errors On Your Website | Matthew Edgar
The most critical question is how do you fix 404 errors? The best way to fix a 404 error is to redirect the...
Read more >What Is a 404 Error? How to Deal With the Web Error
A 404 error indicates that the webpage you're trying to reach can't be found, and usually means that the page has moved or...
Read more >Why URI-encoded ('#') anchors cause 404, and how to deal ...
You get a 404 error because the #callback part is not part of the URL. It's a bookmark that is used by the...
Read more >How to Find and Fix 404 Errors - Neil Patel
Sometimes 404 errors can be the result of changing a page's URL. Altering any part of the URL, whether that's a category name...
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 FreeTop 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
Top GitHub Comments
To anyone coming up on this issue, a quick tip: make sure to do a browser history replace and not push when you advance from the callback URL, otherwise your history will move back to it unexpectedly.
You can enable the logging of
oidc-client-ts
. See here https://authts.github.io/oidc-client-ts/#logging