Skip to content
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

Connection timeout in less than 2 minutes #37

Closed
biafra opened this issue Jan 27, 2014 · 3 comments
Closed

Connection timeout in less than 2 minutes #37

biafra opened this issue Jan 27, 2014 · 3 comments

Comments

@biafra
Copy link

biafra commented Jan 27, 2014

My open websocket dies after 1:30/2:00 minutes. I've created a keepalive mechanism with javascript (periodicaly send something).

Is it the default by specs ?

Thanks!

@joewalnes
Copy link
Owner

This shouldn't happen.

To help me reproduce, please could you tell me which operating system your client and server are running, which browser and if you have any proxies in place?

@biafra
Copy link
Author

biafra commented Jan 27, 2014

Ok. Let me try directly to websocketd without a proxy to recheck if it
happens and I'll report all the info.

On Mon, Jan 27, 2014 at 1:43 PM, Joe Walnes notifications@github.comwrote:

This shouldn't happen.

To help me reproduce, please could you tell me which operating system your
client and server are running, which browser and if you have any proxies in
place?


Reply to this email directly or view it on GitHubhttps://github.com//issues/37#issuecomment-33368083
.

@biafra
Copy link
Author

biafra commented Jan 27, 2014

No issue with websocketd. It was Nginx configuration:

proxy_send_timeout 90;
proxy_read_timeout 90;

Mind you the default for these two settings is 60s.

You can close this then :-)

@biafra biafra closed this as completed Jan 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants