a75458131a
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> |
||
|---|---|---|
| .. | ||
| app | ||
| coap | ||
| dns | ||
| http | ||
| lwm2m | ||
| mqtt | ||
| sntp | ||
| sockets | ||
| CMakeLists.txt | ||
| Kconfig | ||