RE: non - blocking socket nrf9160 HTTP TCP

Albrecht Markus Schellenberger — Thu, 29 Jul 2021 13:22:31 GMT

Hello,

[quote user="haohv6"]Please check and explain what I wrong.[/quote]

Are you using a TLS socket? In this case, my suspicion is that the response data is too large (>2kB, which is our limit in the modem).

[quote user="haohv6"]Moreover, I do http request by a work and submit it to my queue, is there anyway to abort ( or cancel, disable, exit, etc....) that work when socket is blocked[/quote]

Theoretically this is not possible. But in practice you can close the socket from another thread, which should make the recv function to return an error. Another alternative would be to set a timeout on the socket with the setsockopt API. If the socket won't unblock until the timeout expires, it'll return with an error.

Regards,

Markus

RE: non - blocking socket nrf9160 HTTP TCP

haohv6 — Thu, 29 Jul 2021 03:29:15 GMT

Moreover, I do http request by a work and submit it to my queue, is there anyway to abort ( or cancel, disable, exit, etc....) that work when socket is blocked

RE: non - blocking socket nrf9160 HTTP TCP

haohv6 — Thu, 29 Jul 2021 03:23:15 GMT

Hello,

I found this post

https://devzone.nordicsemi.com/f/nordic-q-a/49556/enabling-config_posix_api-w-nrf-v1-0-0-causes-linker-error-for-multiple-definitions-of-fcntl

And I remove nrf API and add Zephyr API, when I send http request, it exit immediately without data.

Please check and explain what I wrong.

int http_request_config(char * http_payload)

{

int ret;

struct sockaddr_in server_sockadd_in;

int server_sock = -1;

memset(&http_req, 0, sizeof(http_req));

memset(http_recv_buf,0,strlen(http_recv_buf));

ret = connect_socket(AF_INET, IOT_SERVER_IP, IOT_SERVER_HTTP_PORT,

&server_sock, (struct sockaddr *) &server_sockadd_in,

sizeof(server_sockadd_in), false);

if (ret >= 0) {

int flags = fcntl(server_sock, F_GETFL, 0);

LOG_DBG(">>>>>>>> nrf_fcntl verified value set to %d\n", flags);

ret = fcntl(server_sock, F_SETFL, flags | O_NONBLOCK);

int rflags = fcntl(server_sock, F_GETFL, 0);

LOG_DBG(">>>>>>>> nrf_fcntl verified value set to %d\n", flags);

http_req.url = url;

http_req.method = HTTP_POST;

http_req.protocol = "HTTP/1.1";

http_req.host = IOT_SERVER_IP;

http_req.payload = http_payload;

http_req.payload_len = strlen(http_payload);

http_req.header_fields = headers;

http_req.response = response_cb;

http_req.recv_buf = http_recv_buf;

http_req.recv_buf_len = sizeof(http_recv_buf);

LOG_DBG("Begin http request");

ret = http_client_req(server_sock, &http_req, 7 * MSEC_PER_SEC, "IPv4 POST");

if (ret < 0) {

LOG_ERR("Fail to request to server!");

}

LOG_DBG("Exit http request");

close(server_sock);

return 0;

}

else {

LOG_DBG("Network err");

close(server_sock);

return -1;

}

/*This is console LOG*/

[00:05:28.680,938] <dbg> tracker_op_mode.tracker_start: ------------------
[00:05:28.688,232] <dbg> tracker_op_mode.tracker_start: --!!!!!!!!!!!!!!!!!!!!!!!!!!!!----------------
[00:05:28.698,303] <dbg> http_common.setup_socket: creat sock = 1
[00:05:28.704,833] <dbg> http_common.connect_socket: Pass setup socket
[00:05:29.241,485] <dbg> http_common.connect_socket: Pass connect
[00:05:29.248,016] <dbg> http_common.connect_socket: Pass ret
[00:05:29.254,211] <dbg> http_requests.http_request_config: >>>>>>>> nrf_fcntl verified value set to 0

[00:05:29.263,977] <dbg> http_requests.http_request_config: >>>>>>>> nrf_fcntl verified value set to 0

[00:05:29.273,773] <dbg> http_requests.http_request_config: Begin http request
[00:05:29.281,463] <dbg> net_http.Data to send
50 4f 53 54 20 2f 54 68 69 6e 67 77 6f 72 78 2f |POST /Th ingworx/
54 68 69 6e 67 73 2f 62 32 65 36 64 31 35 33 2d |Things/b 2e6d153-
37 61 64 36 2d 34 34 37 65 2d 38 63 64 39 2d 62 |7ad6-447 e-8cd9-b
30 34 62 37 63 38 31 38 66 38 38 2f 53 65 72 76 |04b7c818 f88/Serv
69 63 65 73 2f 43 6f 6e 66 69 67 3f 61 70 70 4b |ices/Con fig?appK
65 79 3d 35 34 30 33 62 65 39 37 2d 35 36 36 65 |ey=5403b e97-566e
2d 34 66 39 38 2d 62 36 65 32 2d 65 66 32 30 35 |-4f98-b6 e2-ef205
37 33 34 33 32 64 66 26 41 63 63 65 70 74 3d 61 |73432df& Accept=a
70 70 6c 69 63 61 74 69 6f 6e 25 32 46 6a 73 6f |pplicati on%2Fjso
6e 20 48 54 54 50 2f 31 2e 31 0d 0a 48 6f 73 74 |n HTTP/1 .1..Host
3a 20 31 37 31 2e 32 34 34 2e 31 33 33 2e 32 32 |: 171.24 4.133.22
36 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 3a |6..Conte nt-Type:
[00:05:29.359,741] <dbg> net_http.Data to send
20 61 70 70 6c 69 63 61 74 69 6f 6e 2f 6a 73 6f | applica tion/jso
6e 0d 0a 0d 0a |n....
[00:05:29.377,014] <dbg> net_http.http_client_req: (workqueue): Sent 375 bytes
[00:05:29.384,674] <dbg> net_http.http_client_req: (workqueue): Pass http client init
[00:05:29.392,913] <dbg> net_http.http_client_req: (workqueue): Pass k timeout EQ
[00:05:29.400,787] <dbg> net_http.http_wait_data: http_wait_data running
[00:05:29.407,897] <dbg> net_http.http_wait_data: Pass recv
[00:05:29.413,909] <dbg> net_http.http_wait_data: Connection error (11)
[00:05:29.420,959] <dbg> net_http.http_client_req: (workqueue): Wait data failure (-11)
[00:05:29.429,351] <dbg> http_requests.http_request_config: Exit http request
[00:05:29.436,920] <dbg> net_sock.z_impl_zsock_close: (workqueue): close: ctx=0x00000003, fd=1
[00:05:30.804,138] <dbg> at_cmd.socket_thread_fn: at_cmd_rx 19 bytes, %CESQ: 41,2,10,1

%CESQ: 41,2,10,1

-->When it go into http_wait_data. it return connection error immediately

Thank you

RE: non - blocking socket nrf9160 HTTP TCP

Albrecht Markus Schellenberger — Mon, 26 Jul 2021 09:16:33 GMT

Hello,

when using Zephyr sockets, you should not mix them with the nRF modem library API in your application. Please use the corresponding Zephyr API instead.

However, as shown in the Socket HTTP Client sample, the Zephyr HTTP library only fits to work with blocking sockets, so I do not recommend you switching to non-blocking mode anyway.

Regards,

Markus