Angular2 - How to best handle expired authentication token? : <p>I am using Angular 2.1.2.</p>

<p>I have an authentication token (using angular2-jwt) and if it expires my webApi call fails with a 401 error.  I am looking for a solution where the user will not lose any input data.</p>

<p>I can catch this 401 and open a modal with the login.  The user then logs in, the modal goes away, and they see their input screen.  However, the failed requests are showing errors so I need to reprocess the requests.  If it was a router navigate the initial data has not loaded.</p>

<p>I could reload the page, but if I router.navigate to the same page it does not seem to actually reload the page.  I don't want to do a full page reload on the single page app.  Is there a way to force router.navigate to run, even if it's the current page?</p>

<p>Re-navigating is still a problem because I would lose any new input data that has not saved.</p>

<p>Ideally, the request would just 'pause' until the user logs in from the modal.  I have not found a way to implement this.</p>

<p>Any ideas?
Is there a best practice?</p>
