Skip to content

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

@matthoskins1980

Description

@matthoskins1980

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions