-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send data error handling #1187
Labels
Milestone
Comments
I think it makes totally sense. 👍 |
Do you plan to provide a PR ? |
Yes, I'll just clean the code and start the PR |
Great 🙂 |
PR created: Send data error handling #1188 |
sbernard31
pushed a commit
that referenced
this issue
Jan 7, 2022
sbernard31
pushed a commit
that referenced
this issue
Jan 11, 2022
Signed-off-by: Jarek <jaroslaw.legierski@orange.com> Also-by: Simon Bernard <sbernard@sierrawireless.com>
Implemented by #1195. Thx again @JaroslawLegierski 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We noticed the problem in Leshan with the data received by the server using send data. For instance if the declared model is a Boolean and the data sent is “42”. Currently, it leads to a log error and a stack trace (lwm2m o.e.l.core.californium.LwM2mCoapResource : CodecException: Invalid content X for type X for path X).
We suggest that in this case the server should respond with 400 Bad request instead of 500 server error.
Please find below our proposal solving this problem:
[https://github.com/Przem83/leshan/tree/opl/send_data_error_handling] (Przem83@57e8d07)
@sbernard31 What is your opinion about this solution ?
The text was updated successfully, but these errors were encountered: