OVMS3-idf/components/protocomm/src/transports
Piyush Shah 05852bc4aa 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-05-11 13:01:13 +00:00
..
protocomm_ble.c Unified Provisioning - BLE: Fix characteristics read response issue 2020-02-18 14:42:07 +08:00
protocomm_console.c Protocomm : Session security now supports multiple instances of the same type 2019-04-16 13:47:13 +05:30
protocomm_httpd.c protocomm_httpd: Restart security session if request is received on a new session 2020-05-11 13:01:13 +00:00
protocomm_nimble.c NimBLE: Fix bug in protocomm_nimble chararcteristic access callback 2019-08-15 10:50:30 +08:00