You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When used as a CoAP client, the token is always empty, and the message ID is not set.
This does not cause practical problems as long as they are sent from per-request sockets (as they are in the client example), but if multiple requests are sent to the same client, for example as in
then a CoAP server that does request deduplication will respond to the second request with the time of the first request, rather than with its location.
When used as a CoAP client, the token is always empty, and the message ID is not set.
This does not cause practical problems as long as they are sent from per-request sockets (as they are in the client example), but if multiple requests are sent to the same client, for example as in
then a CoAP server that does request deduplication will respond to the second request with the time of the first request, rather than with its location.
(CC @malishav with whom I encountered this).
The text was updated successfully, but these errors were encountered: