Currently, I am working on implementing an asynchronous method that involves making a POST call to a specific API to fetch data and then storing the result in the user's session. Although the task itself seems straightforward, it becomes challenging when approached in a 'fire-and-forget' style.
Instead of waiting for the response from the external API, I prefer to allow the user to continue navigating to their requested page without any delays. Once the data is retrieved, I want it to be saved in the session.
While everything appears to be functioning correctly, the issue arises when I set the session and move on to the next route, where everything seems to disappear as if it was never stored in the first place. Even after debugging the code that shows no errors, I suspect there might be an issue with setting the session after the response headers have been already set. However, it's puzzling why this would cause a problem.
My current setup involves using nodejs with express for server-side programming and mongodb for handling sessions and databases.
router.get('/myroute', function(req, res, next) {
request({
url: endpoint,
method: "POST",
json: true,
body: jsonData
}, function(error, response, body) {
req.session.mykey = 'some response';
});
res.redirect('/otherroute');
});
router.get('/checkresult', function(req, res, next) {
res.json(req.session.mykey);
});