Issue Summary:
- Having trouble with Express.js redirect functionality.
- The problem occurs when trying to redirect after entering /#impulse, but works fine with /impulse/.
- Server processes the request for /#impulse before applying redirect checks, which results in unsuccessful redirection.
Detailed Explanation:
Currently experiencing an issue where my web app fails to redirect users to the login screen.
To troubleshoot, I modified the code so that all routes containing /impulse/ trigger a particular function:
app.all('/impulse*', function(req, res, next){
isImpulse = true;
console.log('force redirect: ', isImpulse );
next();
});
In order to test further, I removed the res.redirect from the initial function and placed it within the router, setting a global boolean as a temporary solution. The routing section then checks this boolean:
app.get('/impulse', function(req,res){
if(isImpulse){
console.log('enforce redirect');
res.redirect('/auth/login');
return;
} else { impulse.findAll}
} );
Upon testing, I noticed a peculiar behavior.
When accessing /impulse/, the redirect works as expected. However, when using /#impulse/, although the console indicates 'enforce redirect', the actual redirection does not occur, despite the res.redirect call immediately following this log.
I've attempted various modifications to the code, specifically focusing on "app.all". My current code structure eliminates any issues related to "app.all", leaving the root cause attributed to res.redirect failing when /#impulse/ is used.
Two screenshots of the server's console outputs are provided for reference. The first demonstrates successful redirection upon entering /impulse/. The second reveals an issue where even though 'enforce redirect' appears in the console, unwanted content displays before the system enforces redirect rules.
This poses a significant security concern. When accessing /#impulse/, undesirable headers and footers display without proper verification (which should not happen).
The question remains - why does the front-end operation bypass server security measures when processing /#impulse/? It is important to note that app.all is positioned at the beginning of the router to ensure its priority execution.