SLM HTTP client sends #XHTTPCREQ: 0 before body/payload has been sent

[Anthony Ambuehl]

I've recently update to 1.6.1.    

I'm testing with SLM, only modification is using UART2 to support communication with an external mcu on another board.

HTTP client interface code was working with 1.5.1 and is now misbehaving.

After sending command AT#XHTTPCREQ,  I receive OK and then #XHTTPCREQ: 1

My mcu code waits 10 milliseconds before sending the data.  (this seemed to be helpful/necessary on 1.5.1)

Before the 10 milliseconds has elapsed, I receive #XHTTPCREQ: 0

My understanding is that the #XHTTPCREQ: 0 should only be sent after all data was sent.  Since the body has not be send the data is not complete.

[Anthony Ambuehl]

I'm also observing that when I remove the 10 millisecond delay, the XHTTPCREQ: 0 arrives before the OK, which contradicts the example in the documentation.   Seems like XHTTPCREQ is being emitted in an uncontrolled fashion.

[Albrecht Markus Schellenberger]

Hello Anthony,

Can you check my answer in your case #276604 and see if that solves your issue?

Regards,

Markus

[Anthony Ambuehl]

I found an issue in my code which was triggered by the slm_at_httpc sending OK while still in datamode.   I have reported this irregularity in another thread.