BG96 AT+QHTTPPOST error 730 invalid parameter

Hello
GET method is ok
But POST already in error when i use AT+QHTTPPOST (error 730)
Have you got an idea?
Regards.

TX -> ATI
Quectel
BG96
Revision: BG96MAR02A07M1G
OK

TX -> AT+QGMR
BG96MAR02A07M1G_01.007.01.007
OK

TX -> AT+QHTTPCFG=“contextid”,1
OK

TX -> AT+QHTTPCFG=“contenttype”,1
OK

TX -> AT+QIACT?
OK

TX -> AT+QICSGP=1,1,“sl2sfr”,"","",1
OK

TX -> AT+QIACT=1
OK

TX -> AT+QIACT?
+QIACT: 1,1,1,“100.69.67.62”
OK

TX -> AT+QHTTPCFG=“sslctxid”,1
OK

TX -> AT+QSSLCFG=“sslversion”,1,1
OK

TX -> AT+QSSLCFG=“ciphersuite”,1,0x0005
OK

TX -> AT+QSSLCFG=“seclevel”,1,2
OK

TX -> AT+QSSLCFG=“cacert”,1, “cacert.pem”
OK

TX -> AT+QSSLCFG=“clientcert”,1, “clientcert.pem”
OK

TX -> AT+QSSLCFG=“clientkey”,1, “clientkey.pem”
OK

TX -> AT+QHTTPCFG?
+QHTTPCFG: “contextid”,1
+QHTTPCFG: “requestheader”,0
+QHTTPCFG: “responseheader”,0
+QHTTPCFG: “sslctxid”,1
+QHTTPCFG: “contenttype”,1
OK

TX -> AT+QHTTPURL=33,80
CONNECT
OK

TX -> AT+QHTTPPOST=22,80,80
+CME ERROR: 730

Dear Customer,

Pelase add path ahead of the certificate file.
e.g.:
AT+QSSLCFG=“cacert”,1, “ufs:cacert.pem”

Hello, thanks for your reply, but same error.

Did you also add path for “clientcert” and “clientkey”?

Same Error …

Did you upload the certificate files to module? Please refe to FILE_AT command manual to uplaod the certificate file.

No, sorry, but
i don’t understand what i have to do

i follow the exemple : Send HTTPS POST Request and Read the Response, in Quectel_BG96_HTTP(S)_AT_Commands_Manual_V1.0.pdf, and it doesn’t work

You need to get the certificate files form server first, then use AT+QFUPL command to upload the certificates.
You could search AWS IOT website and create an account. Then you can create and manager your devices on the AWS server.

i resolve my problem with

AT+QSSLCFG=“sslversion”,1,4
AT+QSSLCFG=“ciphersuite”,1,0xFFFF
AT+QSSLCFG=“seclevel”,1,0
AT+QSSLCFG=“cacert”,1,“ufs:cacert.pem”
AT+QSSLCFG=“clientcert”,1,“ufs:clientcert.pem”
AT+QSSLCFG=“clientkey”,1,“ufs:clientkey.pem”

Now i have to post a message , i try with POSTMAN with & without requestheader, and it work.

I try without request header with my BG96, it’s work,

But with request header i have a 400 error.

the header is basic
//The HTML Header
const char cc_header01[] = “Content-Type: application/json\r\n”;//32 chars
//Signifies end of Header
const char cc_header02[] = “\r\n”;//2 chars

so --> 34 characters
my message : const char cc_PostMessage[] = “{ “echo” : “bidul” }”;
so = { echo : bidul } --> 20 characters

My QHTTPOST is AT+QHTTPPOST=54,80,80
but doesn’t work.
Have you got an idea?

Regards.

Tha’s expected. In non-request header mode, modem will encapsulate and send the HTTP header automatically, while in request header mdoe, user should add the HTTP header in the post contents.
For example:
AT+QHTTPPOST=170,80

PUT /Willie/QuectelTest.txt HTTP/1.1
Host: 220.180.239.212:8005
Content-Type: text/plain
Accept: /
Content-Length: 43

This text is XXXX HTTP test by using CAT-M.

1 Like

I see the same 730 error on an EC21 when trying to to QHTTPPOST to a HTTPS URL. We’re using non-request mode, and get the error as soon as we run the AT+QHTTPPOST command even without givign the body.

Obviously missing a step somewhere, but not sure what??

Hi Sir,

In EC21A, pelase remove the prefix “ufs:” for the certificates path…