BG77 - Keep getting +QHTTPPOST: 719 error

Hello there,
I’m trying to send HTTP POST request using my BG77 module and include a JSON body.
In order to do that, according to your docs, I set “requestheader” to 1 and send my own POST request.

Here’s my commands sequence:
AT+QHTTPCFG=“contextid”,1 //OK
AT+QHTTPCFG=“sslctxid”,2 //ssl context 2 includes the requires certificates and key, OK
AT+QHTTPCFG=“requestheader”,1 // OK
POST /ctrl/mypost?something=somevalue HTTP/1.1
Content-Type: application/json
Accept: /
Host: myhost
Accept-Encoding: gzip, deflate, br
Connection: Keep-Alive
Content-Length: 20

{“param1”: “value1”}

Why does this error returned? what am I missing?
It’s worth mentioning that HTTPGET works perfectly, but POST not.

Thanks in advance

  1. error 719 means than socket has been closed .

2 two advice :slight_smile:

  1. pls check your ssl certificate first .
  2. I attached one examle for your reference, in this example , it enter header and body as empty .







[2019-11-29_13:52:24:973]+QHTTPPOST: 0,200,91

[2019-11-29_13:52:28:211]HTTP/1.1 200 OK
[2019-11-29_13:52:28:211]Server: openresty/
[2019-11-29_13:52:28:211]Date: Fri, 29 Nov 2019 05:52:24 GMT
[2019-11-29_13:52:28:211]Content-Type: application/json; charset=utf-8
[2019-11-29_13:52:28:211]Content-Length: 91
[2019-11-29_13:52:28:211]Connection: keep-alive
[2019-11-29_13:52:28:211]Strict-Transport-Security: max-age=15724800; includeSubDomains
[2019-11-29_13:52:28:216]cache-control: no-store
[2019-11-29_13:52:28:216]pragma: no-cache
[2019-11-29_13:52:28:216]Access-Control-Allow-Origin: *


[2019-11-29_13:52:28:228]+QHTTPREAD: 0

3 For more analysis , we need to collect modem log , if need to more assistance , pls reach to

Hello @Stephen.Li-Q,
I’ve made some investigation and realized that this error (719) is causes because my POST URL has query parameters in it:

POST /ctrl/mypost?something=somevalue HTTP/1.1

If I remove the ?something=somevalue line, I successfully get response from the server, but I get 400 BAD REQUEST since it must have that query params.
I think you might want to check this issue out…

Thanks again


Recently, I faced the same issue and what I did is that I changed a request string to:
“GET https://xxx/path/mypost?something=somevalue HTTP/1.1
Host: https://xxx

It works for me, so hope it would help you guys too.