Long running Websockets


I host an application that uses long running (4-6 hours) websocket connections. All of the ingress controllers I have tried do work. However they all struggle with time out settings. How does Kong manage this condition? Are there any special settings for websockets that are available in Kong? How does it manage these long running socket connections?