app: coap, http: Add CRLF after data in auto receive mode

Aligns with the behavior of #XRECVFROM and #XRECV.

Signed-off-by: Juha Ylinen <juha.ylinen@nordicsemi.no>

Author: juhaylinen

app/src/sm_at_coap.c

@@ -176,6 +176,8 @@ static void coap_send_data(struct coap_request *req, const uint8_t *payload, siz
 	} else {
 		data_send(req->pipe, payload, payload_len);
 	}
+	/* CRLF after the data chunk, consistent with socket auto-receive behaviour. */
+	rsp_send_to(req->pipe, "\r\n");
 }
 
 /* Notify host that a response block is ready to pull in manual receive mode. */

app/src/sm_at_httpc.c

@@ -511,6 +511,8 @@ static void http_send_data(struct http_request *req, const uint8_t *data, int le
 	} else {
 		data_send(req->pipe, data, len);
 	}
+	/* CRLF after the data chunk, consistent with socket auto-receive behaviour. */
+	rsp_send_to(req->pipe, "\r\n");
 }
 
 /*

doc/app/at_coap.rst

@@ -146,7 +146,7 @@ Unsolicited notification
 
    #XCOAPCDATA: <handle>,<offset>,<length>
 
-The notification line is terminated with ``\r\n`` and the response data follows immediately with no additional separator.
+The notification line is terminated with ``\r\n``, the response data follows immediately, and a ``\r\n`` terminator follows the data bytes.
 In binary mode (default), the data is ``<length>`` raw bytes.
 In hex mode (``<format>=1``), the data is ``2×<length>`` lower-case ASCII hex characters.
 
@@ -221,6 +221,10 @@ CoAP GET (automatic mode, binary):
    AT#XCLOSE=0
    OK
 
+.. note::
+
+   In automatic mode, a ``\r\n`` terminator is appended after the data bytes of each ``#XCOAPCDATA`` notification.
+
 CoAP GET (automatic mode, hex-encoded response, ``format=1``):
 
 ::
@@ -233,6 +237,10 @@ CoAP GET (automatic mode, hex-encoded response, ``format=1``):
 
    #XCOAPCSTAT: 0,69,12
 
+.. note::
+
+   The hex string and the line break after it represent the ``2×<length>`` hex characters followed by the ``\r\n`` terminator.
+
 CoAP GET (manual mode):
 
 ::

doc/app/at_httpc.rst

@@ -127,10 +127,11 @@ Unsolicited notification
 ``#XHTTPCDATA`` is emitted in automatic mode for each received body chunk::
 
    #XHTTPCDATA: <handle>,<offset>,<length>
+   <data>
 
-The notification line is terminated with ``\r\n``.
-In binary mode (``<format>=0``, default), the raw body bytes follow immediately with no additional separator.
-In hex mode (``<format>=1``), ``2×<length>`` lower-case ASCII hex characters follow instead of raw bytes.
+The notification line is terminated with ``\r\n``, the response data follows immediately, and a ``\r\n`` terminator follows the data bytes.
+In binary mode (``<format>=0``, default),  the data is ``<length>`` raw bytes.
+In hex mode (``<format>=1``), the data is ``2×<length>`` lower-case ASCII hex characters.
 
 * The ``<handle>`` parameter is an integer.
   It identifies the socket.
@@ -190,6 +191,10 @@ HTTP GET (automatic mode):
 
    #XHTTPCSTAT: 0,200,261,0
 
+.. note::
+
+   In automatic mode, a ``\r\n`` terminator is appended after the data bytes of each ``#XHTTPCDATA`` notification.
+
 HTTP GET (manual mode):
 
 ::
@@ -222,6 +227,8 @@ HTTP GET with hex-encoded response body (``format=1``, automatic mode):
 
    #XHTTPCSTAT: 0,200,12,0
 
+The hex string and the line break after it represent the ``2×<length>`` hex characters followed by the ``\r\n`` terminator.
+
 HTTP POST with JSON body and custom header:
 
 ::