Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

How to implement a 404 not found that isn't protected #39

Open
matthoskins1980 opened this issue Jan 20, 2021 · 0 comments
Open

How to implement a 404 not found that isn't protected #39

matthoskins1980 opened this issue Jan 20, 2021 · 0 comments

Comments

@matthoskins1980
Copy link

I'm currently implementing a solution that has protected and unprotected routes using the example from Issue #21. That part is working great. I'm trying to implement a catch all 404 page. I'm having difficulty figuring out where to place this. If I place it after the protected routes component, the 404 page gets redirected to my SSO provider.

Is there a way to implement 404 AND have it unprotected?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@matthoskins1980