{"action":"opened","issue":{"url":"https://api.github.com/repos/aspnet/WebSockets/issues/134","repository_url":"https://api.github.com/repos/aspnet/WebSockets","labels_url":"https://api.github.com/repos/aspnet/WebSockets/issues/134/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/WebSockets/issues/134/comments","events_url":"https://api.github.com/repos/aspnet/WebSockets/issues/134/events","html_url":"https://github.com/aspnet/WebSockets/issues/134","id":194239868,"number":134,"title":"Optional keep-alive ping-pongs","user":{"login":"shravan2x","id":4096676,"avatar_url":"https://avatars.githubusercontent.com/u/4096676?v=3","gravatar_id":"","url":"https://api.github.com/users/shravan2x","html_url":"https://github.com/shravan2x","followers_url":"https://api.github.com/users/shravan2x/followers","following_url":"https://api.github.com/users/shravan2x/following{/other_user}","gists_url":"https://api.github.com/users/shravan2x/gists{/gist_id}","starred_url":"https://api.github.com/users/shravan2x/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shravan2x/subscriptions","organizations_url":"https://api.github.com/users/shravan2x/orgs","repos_url":"https://api.github.com/users/shravan2x/repos","events_url":"https://api.github.com/users/shravan2x/events{/privacy}","received_events_url":"https://api.github.com/users/shravan2x/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-08T03:43:51Z","updated_at":"2016-12-08T03:43:51Z","closed_at":null,"body":"I have a server that receives less traffic. This means long-running websockets that are idle for many minutes. On its own, this is alright. But CloudFlare cuts idle sockets after exactly 100s of inactivity. [This](https://stackoverflow.com/questions/39668410/whats-disconnecting-my-websocket-connection-cloudflare-apaches-mod-proxy) post is not mine, but it captures the essence of the problem.\r\n\r\n@Tratcher says in #90 that the current implementation processes these pings anyway. From what I understand, the problem is that both the browser and the server are built to process pings but neither of them actually initiates one. Could we have a way to do this (Maybe a setting while creating them)?"}}
{"actor":{"display_login":"shravan2x"}}