Hey,
I’m currently working with the X-CUBE-ST67W61 Expansion Software Package and the Nucleo-W67x61 board and I am trying to perform an HTTP POST request that sends binary data. For this purpose, I’m using W6X_HTTP_Client_Request together with the content type W6X_HTTP_CONTENT_TYPE_OCTET_STREAM.
The payload I want to transmit contains arbitrary bytes, including 0x00. However, I’ve encountered a problem: as soon as the payload includes a null byte, the HTTP request body seems to be truncated exactly at that point. The server only receives the bytes up to the first 0x00, not the complete buffer. This strongly suggests that the underlying implementation treats the payload as a C-string and therefore stops processing at the first null terminator.
I would like to ask whether this is expected behavior or whether it may be a limitation or bug in the current implementation of the HTTP client. Does W6X_HTTP_Client_Request support sending binary payloads that may contain null bytes or do i need to send my data in ascii?
int32_t http_post_binary_example(void){
ip_addr_t addr = {0};
W6X_HTTP_connection_t settings = {0};
uint8_t server_ip[4] = {192, 0, 2, 1};
const char *method = "POST";
char server_name[] = "example.local";
char uri[] = "/api/echo";
uint16_t port = 11001;
addr.u_addr.ip4 = ATON_R(server_ip);
settings.https_certificate = NULL;
settings.https_certificate_len = 0;
settings.server_name = server_name;
settings.recv_fn = HTTPS_recv_cb_test;
uint8_t bin_payload[6] = { 0x10, 0x00, 0x33, 0x34, 0x35, 0x36 };
W6X_HTTP_Post_Data_t postData = {0};
postData.data = bin_payload;
postData.type = W6X_HTTP_CONTENT_TYPE_OCTET_STREAM;
W6X_Status_t ret = W6X_HTTP_Client_Request(
&addr,
port,
uri,
method,
(const void *)&postData,
sizeof(bin_payload),
NULL, NULL,
NULL, NULL,
&settings
);
if (ret != W6X_STATUS_OK) {
LogError("HTTP request failed\n");
return -1;
}
return 0;
}
Edited to apply source code formatting - please see How to insert source code for future reference.
