1
0
Fork 0
mirror of https://github.com/warmcat/libwebsockets.git synced 2025-03-16 00:00:07 +01:00
libwebsockets/minimal-examples/secure-streams
Andy Green 2cd8f599eb ss: allow url style endpoint addresses
The endpoint field in streamtype policy may continue to just be the
hostname, like "warmcat.com".

But it's also possible now to be a url-formatted string, like, eg,
"https://warmcat.com:444/mailman/listinfo"

If so (ie, if it contains a : ) then the decoded elements may override
if tls is enabled, the endpoint address, the port, and the url path.

No ABI change.
2020-03-15 06:19:38 +00:00
..
minimal-secure-streams ss: allow streamtype policy overlays 2020-03-14 17:04:43 +00:00
minimal-secure-streams-alexa client: secure streams 2020-03-04 12:17:49 +00:00
minimal-secure-streams-avs build: release mode compile fixes 2020-03-10 06:45:24 +00:00
minimal-secure-streams-client-tx client: secure streams 2020-03-04 12:17:49 +00:00
minimal-secure-streams-metadata ss: allow url style endpoint addresses 2020-03-15 06:19:38 +00:00
minimal-secure-streams-proxy client: secure streams 2020-03-04 12:17:49 +00:00
minimal-secure-streams-seq client: secure streams 2020-03-04 12:17:49 +00:00
minimal-secure-streams-sink client: secure streams 2020-03-04 12:17:49 +00:00
README.md client: secure streams 2020-03-04 12:17:49 +00:00

Secure Streams

Secure Streams is a client API that strictly decouples the policy for connections from the payloads. The user code only deals with the stream type name and payloads, a policy database set at lws_context creation time decides all policy about the connection, including the endpoint, tls CA, and even the wire protocol.

name demonstrates
minimal-secure-streams Minimal secure streams client / proxy example
minimal-secure-streams-tx Proxy used for client-tx test below
minimal-secure-streams-client-tx Secure streams client showing tx and rx