Hi,

Is there a way to control TCP/IP settings applied on connections that Knox
accepts? So Knox would ensure something like custom socketOptions
<https://docs.oracle.com/javase/7/docs/api/java/nio/channels/SocketChannel.html#setOption(java.net.SocketOption,%20T)>
are applied by Jetty on an inbound connection.

The specific need I have is to enable TCP keepAlive on WebSocket
connections that Knox is accepting for a backend service. We see
gateways/firewalls timing out TCP connections under these WebSockets if
they are idle for 2-3 mins unless there's TCP keepAlive probes flowing
during the idle period. And since there's usually a user interface on the
other side of a WebSocket it is not unusual for it  to be idle for a few
mins between user activity. Ability to enable TCP keepAlive on the Knox
side has the benefit of not requiring clients to manage the situation.

Regards,
Vin.

Reply via email to