Express / Node.js always responds with HTTP status code 200 about urungi HOT 3 OPEN

The following code segments might be of interest:

And here's how I have attempted to fix this (I'm not an Express / Node.js expert by any means!):

diff --git a/server/app.js b/server/app.js
index 103fef95..2cc94bc0 100644
--- a/server/app.js
+++ b/server/app.js
@@ -136,7 +136,13 @@ for (const routesModule of routesModules) {
 // Catch-all route, it should always be defined last
 app.get('*', function (req, res) {
     res.cookie('XSRF-TOKEN', req.csrfToken(), { sameSite: true });
-    res.render('index', { base: config.get('base') });
+    if ( req.originalUrl === '/' ||
+         req.originalUrl === '/login' ||
+         req.originalUrl === '/home' ) {
+        res.render('index', { base: config.get('base') });
+    } else {
+        res.sendStatus(404);
+    }
 });

 module.exports = app;

from urungi.

The problem here is that the backend does not know about the frontend URLs. So it renders the index page which contains the Angular.js app and let the client's browser do the rest.
Doing what you suggest would prevent linking to (or reloading) pages other than the home page, ie. it will return a 404 for URLs like /dashboards/list whereas it is a valid URL

from urungi.

You might want to try the stop-angularjs branch which is in a work-in-progress state but is usable. It is an ongoing (though in pause at the moment) work to remove angular.js and it uses a more "traditional" way of handling URLs (no client-side routing).
Unknown URLs will return a 404.

from urungi.