React-router intercepting server routes

Version

4.2.2

Steps to reproduce

Have a server that has an endpoint to be directly navigated to (e.g. /api/logout):

app.get('/api/logout', (req, res) => {
  req.logout();
  res.redirect('/');
});

if (process.env.NODE_ENV === 'production') {
  app.use(express.static('client/build'));

  const path = require('path');
  app.get('*', (req, res) => {
    res.sendFile(path.resolve(__dirname, 'client', 'build', 'index.html'));
  })
}

Add navigation in the react app like <a href=“/api/logout”> or window.location = ‘/api/logout’

Expected Behavior

A page refresh to the same domain through <a> tag navigation or setting window.location should go through server routing before loading the react app.

Actual Behavior

The correct route request isn’t made to the server and the route is treated as a react-route.

This behavior is only experienced in a production environment. However, there is a strange case where everything works as intended. In firefox private browsing, routing works correctly. In regular firefox, regular chrome, and incognito chrome, routing is not working, as described above.

[dev-grant]

@pshrmn @timdorr I fixed things by removing the registerServiceWorker() from the create-react-app boilerplate.

[jrrcdev]

Removed registerServiceWorker and unregister fix this issue, what this registerServiceWorker do to fuck everything?