SPWF04S Receiving POST data

[tabekb]

Posted on May 17, 2017 at 14:28

I am trying to send data from the browser to the module using POST request with output_demo.html.

The POST request is limited to 64 bytes, so I cannot send more than 64 bytes with a POST...If I send 65 bytes, the last byte is truncated and only 64 bytes are delivered by the module. Is this a limitation of the module? Can be the number of bytes increased? 64 bytes for a POST are not enough...

I send this from browser : Output=SetNetSet{6;1;0;2;1;0;172.10.20.1;123456789012345;123456789012345678}

There are 68 bytes of data in the above request.

The module outputs this on uart console: +WIND:57:Output from remote:64:SetNetSet{6;1;0;2;1;0;172.10.20.1;123456789012345;123456789012345

The module outputs only 64 bytes, but the request contains 68 bytes...

Thanks

[Mario Ghecea]

Posted on October 31, 2017 at 01:32

According to the Certificate Error : 19, returned by firmware socket, that message means that the certificate is not supported!

[Mario Ghecea]

Posted on October 31, 2017 at 01:23

Yup, thanks for that suggestion I upgraded to the SPWF04...

[Mario Ghecea]

Posted on October 31, 2017 at 01:30

Now I'm having a different issue with FRED and websockets...I'm getting certificate issues...

I post to my node-red installation on FRED via websocket (tests ok from my javascript and posts fine to FRED) but has issues from hardware on SPWF04SA...

My websocket connects internally to an MQTT broker, which I could not get going directly, no matter what I do...But it seems I'm also having issues connection to the websocket as well...Seems no matter what I post to FRED, I have created all sorts of endpoints, these secure connectivity issues persist! 

AT+S.WSOCKON=dreamsmatrix.fred.sensetecnic.com,443,/api/public/mqtt,2,,,,,

AT-S.Certificate Error:19

AT-S.WebSocket Client Error:1

AT-S.ERROR:74:Failed to open socket

Any idea how to get around this issue, Gerardo ?

Cheers,

Mario G.

[Mario Ghecea]

Posted on October 31, 2017 at 03:05

Same thing happens when I send any TLS requests...Any way to setup the certificate option for SSL ? I don't have much documentation on that...I believe its an

https://community.st.com/external-link.jspa?url=https%3A%2F%2F

request according to CURL, which works by the way and so do websockets sends from java scripts. I just need to enable certificates on the firmware ?

AT+S.HTTPPOST=dreamsmatrix.fred.sensetecnic.com,/api/public/magnum/wifi/{'Data':'12345'},443,2,,,,

AT-S.Certificate Error:19

AT-S.Http Client Error:2

AT-S.ERROR:111:Request failed

[Gerardo GALLUCCI]

Posted on November 04, 2017 at 11:28

FW1.0.0 only supports RSA-based certificates. No ECC-based certificates. What kind on certificates are you using? Please refer to AN4963

[Mario Ghecea]

Posted on November 08, 2017 at 04:41

Yup I'm missing the server side certificates...Seems anonymous mode does not get supported in TLS2.0.