Michael Scott a75458131a net: lib: app: trigger TLS closure when connection is closed ... When testing TLS connections on production web server, it was noticed that the TLS mainloop was getting "hung" after a connection was made via HTTPS and then closed by the server. The TLS mainloop was never being notified that the connection was closed and was stuck waiting for more data. The next time that connection was used, TLS would fail to start. Let's force trigger a closure of the TLS process when the net-app layer is notified of the connection closure. This allows the connection to be successfully reused later. Signed-off-by: Michael Scott <michael@opensourcefoundries.com>		2018-01-10 21:47:46 -05:00
..
ip	net: shell: conn: Cross-ref TCP control block to owning context	2018-01-04 18:38:19 -05:00
lib	net: lib: app: trigger TLS closure when connection is closed	2018-01-10 21:47:46 -05:00
buf.c	net: buf: Add slist helpers	2017-11-06 14:20:40 +02:00
CMakeLists.txt	net/ieee802154: Make RAW mode generic	2017-11-22 10:10:09 -05:00
hostname.c	net: Add hostname setting to Kconfig	2017-10-17 08:36:39 -04:00
Kconfig	net: Kconfig: Don't select STDOUT_CONSOLE	2018-01-05 10:00:26 -05:00
Kconfig.hostname	net: Add hostname setting to Kconfig	2017-10-17 08:36:39 -04:00
TODO	Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_*	2017-08-09 11:14:19 +03:00