detect non-existing route on the server side
See original GitHub issueI’ve got a simple express app that follows the basic structure as described in the server-rendering guide.
My routes are fully defined in the react-router
style so I don’t want to add server-side routes for this part of the app.
I would like to set the correct response status when I’m trying to render a route that does not exist (apart from rendering it with the DefaultRoute
. Is there a way to detect wether Router.run
picked an existing route or went to the fallback route at server-side?
Issue Analytics
- State:
- Created 9 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
detect non-existing route on the server side #573 - GitHub
I've got a simple express app that follows the basic structure as described in the server-rendering guide. My routes are fully defined in ......
Read more >reactjs - How to detect 404 routes (NoMatch) when doing SSR ...
I'm using react-router-dom and I'm implementing SSR (Server Side Rendering) to my web app. I'm having trouble on how to handle 404 routes....
Read more >Troubleshoot issues with DNS record resolution for public ...
To find the authoritative name servers, check the value in the name server (NS) resource record set of the Route 53 public hosted...
Read more >React Router DOM: How to handle routing in web apps
How to set the default route in React. To demonstrate how React Router DOM works, we'll create an example React app. You can...
Read more >Verify Azure ExpressRoute connectivity - troubleshooting guide
This article helps you identify if and where a connectivity issue ... multiple routing configurations based on external BGP (eBGP) can be ...
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
Wow, seems a lot of work for something that simple.
I’m taking another approach now. I just name the
NotFound
handler and than look for that name inRouter.run
on the server side:@ESTEBANMURUZABAL You have been commenting on a number of long dead issues. Please use StackOverflow or Reactiflux for asking questions.