21697b3210
Normally when doing a Client Connection Error handling, we can action any ss relationship straight away since we are in a wsi callback without any ss-aware parents in the call stack. But in the specific case we're doing the initial onward wsi connection part on behalf of a ss, in fact the call stack does have earlier parents holding references on the related ss. For example secstream_h1 (ss-h1.c:470) CCE lws_inform_client_conn_fail (close.c:319) fails early lws_client_connect_2_dnsreq (connect2.c:349) lws_http_client_connect_via_info2 (connect.c:71) lws_header_table_attach (parsers.c:291) rops_client_bind_h1 (ops-h1.c:1001) lws_client_connect_via_info (connect.c:429) start onward connect _lws_ss_client_connect (secure-streams.c:859) _lws_ss_request_tx (secure-streams.c:1577) lws_ss_request_tx (secure-streams.c:1515) request tx ss_cpd_state (captive-portal-detect.c:50) lws_ss_event_helper (secure-streams.c:408) lws_ss_create (secure-streams.c:1256) SS Create Under these conditions, we can't action the DESTROY_ME that is coming when the CCE exhausts the retries. This patch adds a flag that is set during the SS's onward wsi connection attempt and causes it to stash rather than action the result code. The result code is brought out from the stash when we return to _lws_ss_client_connect level, and passed up in the SS flow until it is actioned, cleanly aborting the ss create. |
||
|---|---|---|
| cmake | ||
| contrib | ||
| doc-assets | ||
| include | ||
| lib | ||
| lwsws | ||
| minimal-examples | ||
| plugin-standalone | ||
| plugins | ||
| READMEs | ||
| scripts | ||
| test-apps | ||
| win32port | ||
| .gitignore | ||
| .mailmap | ||
| .sai.json | ||
| bug_report.md | ||
| changelog | ||
| CMakeLists-implied-options.txt | ||
| CMakeLists.txt | ||
| component.mk | ||
| Kconfig | ||
| libwebsockets.dox | ||
| LICENSE | ||
| Makefile.projbuild | ||
| README.md | ||
Libwebsockets
Libwebsockets is a simple-to-use, MIT-license, pure C library providing client and server for http/1, http/2, websockets, MQTT and other protocols in a security-minded, lightweight, configurable, scalable and flexible way. It's easy to build and cross-build via cmake and is suitable for tasks from embedded RTOS through mass cloud serving.
80+ independent minimal examples for various scenarios, CC0-licensed (public domain) for cut-and-paste, allow you to get started quickly.
There are a lot of READMEs on a variety of topics.
We do a huge amount of CI testing per push, currently 495 builds on 27 platforms.
News
Request for help on mp4 / h.264 / libav*
If you're interested in ws + h.264, there's a 80-90% complete minimal example that needs help with the mp4 container part, the lws v4l2 integration, MPJPG->h.264 transcoding and ws transport to MediaSource parts already work.
Take a look at the top two patches on _v4l2 branch and post on the mailing list or
github to discuss if you can help.
v4.2 is released
See the changelog
Transition from master branch to main branch
The master->main branch transition happened several months ago, currently master is still around as a mirror of main. master branch will go away some time before the next release.
Support
This is the libwebsockets C library for lightweight websocket clients and servers. For support, visit
and consider joining the project mailing list at
https://libwebsockets.org/mailman/listinfo/libwebsockets
You can get the latest version of the library from git:
Doxygen API docs for development: https://libwebsockets.org/lws-api-doc-master/html/index.html