Open TomazCebekAstron opened 1 year ago
This is your documented message in hex format: 4002000461005d0a70732f53502f3836303031363034303633323333382f434d0b636c69656e7469643d3836303031363034303633323333380d03746f6b656e3d34303935303135313730 And the master branch server returns: 60800004 <--- 4.00 Bad request
also example of: connection mode subscribe is just publish copy this is not actuall example of the subscribe... coap-client -m post -e "Hi, this is libcoap" "coap://127.0.0.1/ps/coap/test&clientid=123&token=3404490787"
mqtt/{+topic}{?QueryString*}
in CN version you have ps written... and ps works... change from mqtt to ps...
"coap://127.0.0.1/ps/coap/test&clientid=123&token=3404490787" this will result in 3 uri-path options... how is it possible that you do not use percent encoding...
change into this: "coap://127.0.0.1/ps/coap%2Ftest&clientid=123&token=3404490787" only like this will anything acceptable come out...
File: /en_US/gateway/coap.md
2.05: Subscribe successfully <--- the server actually responds with 2.04 changed... but even with this the coap client does not seem to be subscribed... Request: 4002000461005270730d0753502f3836303031363034303633323333382f434d0b636c69656e7469643d3836303031363034303633323333380d03746f6b656e3d33373733363235373931 <-- ps needs to be seperate uri-path option Response from the server: 60440004