-
Notifications
You must be signed in to change notification settings - Fork 423
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
coap-client gets stuck with large .well-known/core response #1473
Comments
Thanks for raising this. |
I'm not able to reproduce this with a 6302 byte long response using latest develop code 7551d2e for coaps using PSK.
Were you using code from #1469 - I did find a late fix this which could explain what you are seeing. |
Sorry, my mistake. I accidentally used the system coap-client not the one I built from the repo. With the one from the develop branch it works as expected. Thank you! |
My CoAP server returns a large string for
.well-known/core
requests. When I request this resource with coap-client, it gets stuck and does not terminate. When I request this with my own client, I get the complete response. The following logs are from different runs, so the numbers will not match, sorry. I just noticed when I finished writing this report.The coap-client output:
The server output with coap-client:
and no further communication after the last line.
With my client:
and more lines after that.
This happens with current develop branch and with my last PR commit 782e607.
This is not a problem for me, I just noticed this by accident.
The text was updated successfully, but these errors were encountered: