A global error handler where all the exceptions end. The error handling is part of a interception chain, which follow this order: global error -> http error -> auth request. The requests follow this order, and the responses come in the opposite direction.
Login checking: here there was a deep bug. When accesing to a protected frontend route, if the token parsing failed, the execution thread stopped. So in case of a user trying to access a protected route without being logged, the behavior was the default by Angular but the "canActivate" method wasn't being executed so the user wasn't properly redirected to /login
Mainly two features: