atclient_connection_send fails to send cram command to secondary server

[srieteja]

Describe the bug

I have been trying to send the cram command to the secondary server. The mbedtls_ssl_write (used by atclient_connection_send) somehow returns a valid int value but the cram command is not received on the server side. Then the program exits with 'mbedtls_ssl_read failed with exit code -26624' (26624 converted to hex is 0x6800).

Note that the rest of the commands before cram - fetching secondary address from root server and fetching challenge from secondary(from:@atsign) are executing as expected.

Steps to reproduce

1. First I 'fetch the challenge from the server'
2. Then I 'generate a digest with this challenge and cram secret'
3. And then 'send the command cram:digest/r/n'
4. This command does not reach the server and also the existing socket is terminated

Expected behavior

The command should go through to the server and the server should respond with 'data:success'

Screenshots

Note: The server is using my local time but the client seems to be using UTC

Server:

Client:

Additional context

No response

[JeremyTubongbanua]

Are you remembering to add \r\n at the end of the src buffer?
Also make sure not to send the null-terminator.

So sending cram:$digest\r\n is right, but cram:$digest\r\n\0 might give you that error