esp-idf/components/protocomm
Piyush Shah f677655fcb protocomm_httpd: Restart security session if request is received on a new session
This commit fixes a bug as well as changes a behaviour.

Bugfix: During softap/httpd based provisioning, if a session was closed
midway and a new one started, it would never proceed if the http server
assigns same socket number to the new session (which happens almost always).
Now, if a session is closed, using the http callbacks, the older session
data is cleared so that a new one can be created.

Behavioural change: If a client (mobile app particularly) does not use
persistent http session i.e. all provisioning communication on the same
socket, the provisioning may fail. Earlier, since the session context was
not getting cleared, even if the client closed a session and continued
on a new one, it would go through if the socket number assigned was same
(which happens almost always).

Ideally, from a security perspective, all communication related
to secure provisioning must happen on the same socket, and so, this
change is required.
2020-06-10 01:25:53 +05:30
..
include ESP Local Control Feature Added 2019-07-03 21:31:04 +05:30
proto cmake : Add CMakeLists.txt and update READMEs for re-compilation of proto files 2019-07-05 18:20:15 +05:30
proto-c Protocomm : Added unit tests and protobuf-c generated files 2018-10-02 19:07:28 +05:30
python Protocomm : Added unit tests and protobuf-c generated files 2018-10-02 19:07:28 +05:30
src protocomm_httpd: Restart security session if request is received on a new session 2020-06-10 01:25:53 +05:30
test components: use new component registration api 2019-06-21 19:53:29 +08:00
CMakeLists.txt NimBLE-provisioning: Add NimBLE support to unified provisioning framework 2019-07-02 14:20:10 +08:00
component.mk NimBLE-provisioning: Add NimBLE support to unified provisioning framework 2019-07-02 14:20:10 +08:00