When reloading the page on any other route than the base route ("/"), we encounter a 404 error (see Figure 1). We encounter this error because the backend server does not realize that this route belongs to our frontend. We want Angular content to serve that route and not the backend server (except anything prefixed with /api and other login routes).
TODO
[ ] Fix the 404 error by making Angular serve this route and not the backend server (in other words, it should load the webpage at the route not make some kind of api request (unless it really is)
Notes
Figure 1. Result from refreshing the frontend on the /jobs route.
Context
When reloading the page on any other route than the base route ("/"), we encounter a 404 error (see Figure 1). We encounter this error because the backend server does not realize that this route belongs to our frontend. We want Angular content to serve that route and not the backend server (except anything prefixed with
/apiand other login routes).TODO
Notes
/jobsroute.