There's something we haven't used yet: the possibility of directly navigating to a given route or going back to the previous location and more. Whenever a <Route> is matched, the rendered component gets some special props, which you can use:

• this.props.history, providing access to the browser history, with several methods like .goBack() to return to the previous page, or .push("someURL") to navigate to a different page; see https://developer.mozilla.org/en-US/docs/Web/API/History_API and especially https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/api/history.md for more on this
• this.props.location, with several properties related to the current location and its URL; see https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/api/location.md for extra data
• this.props.match, which tells you how the current route was matched; see https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/api/match.md

So, we are now able to work with routes; let's move on to routes needing authorization.