nRF9160-DK HTTP POST REQUEST

RE: nRF9160-DK HTTP POST REQUEST

Gioele — Thu, 22 Sep 2022 08:33:58 GMT

Probably the server wasn't running but now everything is fine. We understood that the solution is the "/" that you mentioned plus the correct "content-length" of the body. Thank you!

RE: nRF9160-DK HTTP POST REQUEST

Didrik Rokhaug — Wed, 21 Sep 2022 14:41:39 GMT

Is the server running?

I am trying to send the request myself, but the connection to the server times out.

RE: nRF9160-DK HTTP POST REQUEST

Gioele — Tue, 20 Sep 2022 14:39:38 GMT

We tried to add a "/" but we have the same error. This is the exact request that we make on Postman.

RE: nRF9160-DK HTTP POST REQUEST

Didrik Rokhaug — Tue, 20 Sep 2022 14:32:50 GMT

No, that is the hostname. You also need the path to the resource you want to get/modify.

Try add a '/' between the request method and the protocol version (separated by spaces), if you want to modify the root object.

RE: nRF9160-DK HTTP POST REQUEST

Gioele — Tue, 20 Sep 2022 14:10:08 GMT

This is the URL #define HTTPS_HOSTNAME "ec2-184-73-45-204.compute-1.amazonaws.com"

If I make the same request on PostMan it runs!

RE: nRF9160-DK HTTP POST REQUEST

Didrik Rokhaug — Mon, 19 Sep 2022 12:39:33 GMT

Where?

I still don't see any URL between the request method (POST) and the protocol version (HTTP/1.1)

RE: nRF9160-DK HTTP POST REQUEST

Gioele — Mon, 19 Sep 2022 12:24:03 GMT

The URL is included!

#define HTTPS_PORT 8545

#define HTTPS_HOSTNAME "ec2-184-73-45-204.compute-1.amazonaws.com"
#define BODY  "{ \"jsonrpc\": \"2.0\", \"method\": \"eth_chainId\" }"



#define HTTP_HEAD "POST HTTP/1.1\r\n"\
		"Host: "HTTPS_HOSTNAME"\r\n"\
		"Connection: close\r\n"\
	    "Content-type: application/json\r\n"\
		"\r\n"\
		""BODY"\r\n\r\n"

void main(void)
{
	int err;
	int fd;
	char *p;
	int bytes;
	size_t off;
	struct addrinfo *res;
	struct addrinfo hints = {
		.ai_family = AF_INET,
		.ai_socktype = SOCK_STREAM,
	};

	printk("HTTPS client sample started\n");

// #if !defined(CONFIG_SAMPLE_TFM_MBEDTLS)
// 	/* Provision certificates before connecting to the LTE network */
// 	err = cert_provision();
// 	if (err) {
// 		return;
// 	}
// #endif

	printk("Waiting for network.. \n");
	err = lte_lc_init_and_connect();
	if (err) {
		printk("Failed to connect to the LTE network, err %d\n", err);
		return;
	}
	printk("OK\n");

	err = getaddrinfo(HTTPS_HOSTNAME, NULL, &hints, &res);
	if (err) {
		printk("getaddrinfo() failed, err %d\n", errno);
		return;
	}

	((struct sockaddr_in *)res->ai_addr)->sin_port = htons(HTTPS_PORT);

	if (IS_ENABLED(CONFIG_SAMPLE_TFM_MBEDTLS)) {
		fd = socket(AF_INET, SOCK_STREAM | SOCK_NATIVE_TLS, IPPROTO_TCP);
	} else {
		fd = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP);
	}
	if (fd == -1) {
		printk("Failed to open socket!\n");
		goto clean_up;
	}

	// /* Setup TLS socket options */
	// err = tls_setup(fd);
	// if (err) {
	// 	goto clean_up;
	// }

	printk("Connecting to %s\n", HTTPS_HOSTNAME);
	err = connect(fd, res->ai_addr, sizeof(struct sockaddr_in));
	if (err) {
		printk("connect() failed, err: %d\n", errno);
		goto clean_up;
	}

	off = 0;
	do {
		bytes = send(fd, &send_buf[off], HTTP_HEAD_LEN - off, 0);
		if (bytes < 0) {
			printk("send() failed, err %d\n", errno);
			goto clean_up;
		}
		off += bytes;
		printk("\n>\t %s\n\n", send_buf);


	} while (off < HTTP_HEAD_LEN);

	printk("Sent %d bytes\n", off);


	off = 0;
	do {
		bytes = recv(fd, &recv_buf[off], RECV_BUF_SIZE - off, 0);
		if (bytes < 0) {
			printk("recv() failed, err %d\n", errno);
			goto clean_up;
		}
		off += bytes;
		printk("Sto ricevendo bytes\n");
		printk("%d bytes\n", bytes);

	} while (bytes != 0 /* peer closed connection */);

	printk("Received %d bytes\n", off);

	/* Print HTTP response */
	p = strstr(recv_buf, "\r\n");
	if (p) {
		off = p - recv_buf;
		recv_buf[off + 1] = '\0';
		printk("\n>\t %s\n\n", recv_buf);
	}

	int tot_num_bytes = 0;

	printk("Finished, closing socket.\n");
	freeaddrinfo(res);

(void)close(fd);

	lte_lc_power_off();
	
clean_up:
	freeaddrinfo(res);
	(void)close(fd);

	lte_lc_power_off();
}

RE: nRF9160-DK HTTP POST REQUEST

Didrik Rokhaug — Mon, 19 Sep 2022 08:18:27 GMT

I had another look at the request you are sending, and it does not look like you have the URL included in the request line.

RE: nRF9160-DK HTTP POST REQUEST

Gioele — Sat, 17 Sep 2022 10:32:07 GMT

The request is correct, we make the same request in Postman.
When we try to print the request, we do not always have the result, but when there is, it is correct. Could it be that there is another way to send the body? It is a JSON.

RE: nRF9160-DK HTTP POST REQUEST

Didrik Rokhaug — Fri, 16 Sep 2022 11:01:16 GMT

Then your problem is something else.

Have you tried to print the request, to make sure it is what you want?

Have you tried to send the same request from another client, to make sure that the request itself is okay?

RE: nRF9160-DK HTTP POST REQUEST

Gioele — Fri, 16 Sep 2022 10:54:52 GMT

#define HTTP_HEAD "POST HTTP/1.1\r\n"\
		"Host: "HTTPS_HOSTNAME"\r\n"\
		"Connection: close\r\n"\
	    "Content-type: application/json\r\n"\
		"\r\n"\
		""BODY"\r\n\r\n"

Same problem!

RE: nRF9160-DK HTTP POST REQUEST

Didrik Rokhaug — Fri, 16 Sep 2022 10:25:52 GMT

Hi,

The header is separated from the body with an empty line, consisting of a carriage return and a line feed.

https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#HTTP/1.1_request_messages

Best regards,

Didrik