Open Talha76 opened 11 months ago
Update: As far I understood, this issue occured due to the following code:
app.use(session({
secret: "secret",
resave: true,
saveUninitialized: true // mainly due to this
}));
But when I recoded saveUninitialized: false
, this issue was removed, I don't know why.
any update?
@VigilioYonatan Same issue persists. But I can't find out the exact reason.
A cool way to reproduce this issue:
const app = require('express')();
const session = require('express-session');
app.get('/', (req, res) => {
res.send("cool")
});
app.use(session({
secret: "asdasd"
}))
app.get('/test', (req, res) => {
res.send("cool")
})
app.listen(3000, () => {
console.log('Server is running on port 3000');
})
127.0.0.1:3000/
will work
127.0.0.1:3000/test
will not work
Any update?
I encounter the same issue and no solve so far. The problem only occurs in Postman but not in curl.
Same problem here, I'm using express and express-session. Oh god, please help me
What version of Bun is running?
1.0.16+800fb1290
What platform is your computer?
Linux 5.15.0-91-generic x86_64 x86_64
What steps can reproduce the bug?
When I make a request from postman on the server running with bun, it gives me the following error, (I execute
bun start
to start sever withbun run index.js
): But when I run the server with npm, and I make a request to the same URL, it gives the expected output. I executebun dev
to start server with script:nodemon index.js
:To reproduce the bug,
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
Here is my
package.json
: