felixge / felixge/tcpkeepalive
Could you ever support tls.Conn?
Open
- Dominant language
- Go
- Stars
- 248
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
When I am connecting a websocket via wss:// and I try to pass the tls.Conn which is the ".UnderlyingConn()" of the response of the Dial, but it immediately bails out with an error because it's not a net.TCPConn. Why can't secure tcp sockets be kept alive like unsecured tcp sockets?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.