Here is my express code where I am utilizing express-session to manage storage and work with cookies. Since version 1.5.0, the module no longer requires cookie-parser to handle storing the cookie in req/res.
The session data is stored in a PSQL database hosted on ElephantSQL.
The following code shows the cors configuration of my express application and how I handle req.body:
The application is live on Railways.app:
Below is the code for making POST requests to the API in my front-end application using React and Axios:
The issues I'm facing include:
When running the app and attempting to log in, no cookie is stored in the browser. Strangely, it creates two sessions in the database. However, when I run the Node app locally and make a request to localhost from my front-end, everything works smoothly - only one session is created with the cookie being stored.
Based on logic, when posting a username or password that doesn't exist, it should return a 404 error but instead, it returns a 401 error which is unexpected. Again, this issue is only present when running the server locally.
When using Insomnia to send post requests to the deployed server via the URL, the behavior is as expected - cookies are stored correctly and only one session is created.