libwebsockets | Websockets server/client library in pure C | Websocket library

I'm trying to cross compile libwebsockets for arm. I put OpenSSL and Zlib path in CMakefiles.txt. But after command "make", it makes error.

OpenSSL and Zlib path setting in CMakefiles.txt

I'm trying to cross compile aws webrtc library(https://github.com/awslabs/amazon-kinesis-video-streams-webrtc-sdk-c) for arm. So I followed the instruction on Readme.md but I failed.

What I did

I am building a client/server protocol using libwebsockets library. In the poll thread, each callback on incoming packets triggers a certain method to either save data, respond accordingly, and so on. However, if there are other incoming packets that would trigger LWS_CALLBACK_CLIENT_RECEIVE, the processing of the previous task is left undone.

Is there a way to finish the tasks before dealing with the packets received? Should LWS_CALLBACK_CLIENT_RECEIVE start new threads to handle the processing of data?

I'm trying to run mosquitto with config:

I'am using libwebsockets library to create a c client which call ibm- watson speech to text server. So i've used minimal-ws-client-rx exemple https://github.com/warmcat/libwebsockets/blob/master/minimal-examples/ws-client/minimal-ws-client-rx/minimal-ws-client.c and then i changed the i.address to "gateway-lon.watsonplatform.net" and i.path to "/speech-to-text/api/v1/recognize?apikey:Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" when i try to run the code it gives me:

NOTICE: created client ssl context for default WARN: lws_client_handshake: got bad HTTP response '401' ERR: CLIENT_CONNECTION_ERROR: HS: ws upgrade unauthorized but when i change i.port to 80 the error is:

NOTICE: created client ssl context for default ERR: CLIENT_CONNECTION_ERROR: Timed out waiting SSL USER: Completed Failed

the whole code is :

/* * lws-minimal-ws-client * * Copyright (C) 2018 Andy Green * * This file is made available under the Creative Commons CC0 1.0 * Universal Public Domain Dedication. * * This demonstrates the a minimal ws client using lws. * * It connects to https://libwebsockets.org/ and makes a * wss connection to the dumb-increment protocol there. While * connected, it prints the numbers it is being sent by * dumb-increment protocol. */

According to https://blog.kitware.com/cmake-finding-qt5-the-right-way/, the method find_package(Qt5 COMPONENTS Core Qml Quick Svg Qt5WebSockets REQUIRED) allows me to load lots of QT5 packages while being able to set the QT root only once by setting the Qt5_DIR variable. I'm trying to compile a minimal CMake project which is listed below, using this technique. You can see that WebSockets isn't found. What is the problem?

PS: My home directory at /home/lz/Qt5.11.2 indeed has a new Qt installation that Qt installer just installed for me, and it indeed has libwebsockets and websocket include files.

My CMakeLists.txt:

I want to use libwebsockets in a foreign libuv loop. My code (inspired from this simple example) compiles and links correctly, but at execution, on webpage request, the browser never receives a response from the server.

I build both libwebsockets (v3.1.0) and libuv (v1.25.0) from the sources in my cmake. I use the following command line:

I'm using the libwebsockets v2.4.

The doc seems unclear to me about what I have to do with the returned value of the lws_write() function.

If it returns -1, it's an error and I'm invited to close the connection. That's fine for me.

But when it returns a value that is strictly inferior to the buffer length I pass, should I consider that I have to write the last bytes that could not be written later (in another WRITABLE callback occurrence). Is it even possible to have this situation?

Also, should I use the lws_send_pipe_choked() before using the lws_write(), considering that I always use lws_write() in the context of a WRITABLE callback?

I am trying to work with an API of one device, but it is using a WS interface with enforced Origin header, which is giving me troubles.

In Chrome, I can open the Console while a page with the correct Origin is loaded, create the WS connection, and send/receive messages without difficulties: Note that sent messages (in green) are always acknowledged by the server.

For reference, this is what happens if I create the connection on a different page, which results in an Origin header mismatch, reported as 404:

To sidestep this problem, I turned to C, because the rest of my program is written in that anyway. This is the code I have right now, based mostly on this answer: