-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Transport timeout too short cause Transport close.. #403
Transport timeout too short cause Transport close.. #403
Comments
Let's see if this pull request solves the issue. I had similar client issues |
sockjs#403 Provide SockJS config for minimum transport fallback timeout
Hi, are the PR 412 and 413 sufficient to close this issue and release this feature in the next release please? thanks. |
1.3.0 doesn't have the transport timeout configuration feature. Is there a beta release or do I just need to build my own until it gets released? The current calculated timeout is way too short for my app. |
@chrislhardin The referenced PR #413 has not been merged, thus it is not in master yet. |
my connect code
i found code at "SockJS.prototype._connect"
i log the timeoutMs is 698
in "websocket" my server reponse may be than this time... how to change it , did it has a setting ?
The text was updated successfully, but these errors were encountered: