-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request hangs somehow #24
Comments
Hmm, could be that the problem is even deeper in express-session, since penetrating with:
when "store" is memory
leads to 16 completed requests... |
So it looks like express folks are looking into this. Do you want to keep this issue open? |
Hello, |
closing this for the reasons explained in expressjs/session#91 |
Starting this trivial static file sever:
and testing it with apache bench
leads to the Problem that the second request is never being answered.
If issuing manual several test with
every thing is ok.
Using a memory store session by commenting out the "store" property works also OK even with:
I came to this striped down example from a much bigger one, where I have the problem that "sometimes" request do not get answered and time out...
Any ideas?
Thanks
Ognian
The text was updated successfully, but these errors were encountered: