Mikhail Macherkevich
Mikhail Macherkevich
Second this. Matomo is great and having an easy way to use it (or at least a guide) will be great.
Great feature to have. Subscribed.
So... still no fixes or even nice workarounds? req.session.save() does not help
Hi Doug. You mentioned putting redirect in a **save** callback here `https://github.com/expressjs/session/issues/526#issuecomment-346944647`. I guess it really does not help? (I was thinking maybe I am doing something wrong)
It does not, but maybe some other parts of app are screwing something. I will try to set a test stand based on @antishok gist and be back with results.
resave & saveUninitialized set to false are *not* doing the trick. Big part of the problem for me, is that I can not reproduce this bug (?) in 100% cases....
On my version of @antishok gist, with difference in store - I use mongo gives me same results for Chrome: https://pastebin.com/xiUkJvcy Firefox: https://pastebin.com/GLhsLDnz I am kinda lost here. I was...
I think I pinned down the problem. Please take a look at this [gist](https://gist.github.com/Amantel/e96206528c4fd621c88e92510b2569f8) For me this works as intended (bad :) ) ~~on server (with qualified domain name etc.)...
Changed code to call redirect only after manual save. ``` if (req.query.yes) { req.session.userAuthed = 1; req.session.save(() => { return res.redirect("/"); }); } else { return res.redirect("/"); } ``` Does...
@HarshithaKP thanks! I kinda moved past this, but I will try to see if my gist is working now, thanks!