mirror of
https://github.com/warmcat/libwebsockets.git
synced 2025-03-30 00:00:16 +01:00
704eaa5e63
Make the policy load apis public with an extra argument that says if you want the JSON to overlay on an existing policy rather than replace it. Teach the stream type parser stuff to realize it already has an entry for the stream type and to modify that rather than create a second one, allowing overlays to modify stream types. Add --force-portal and --force-no-internet flags to minimal-secure-streams and use the new policy overlay stuff to force the policy for captive portal detection to feel that there is one or that there's no internet. |
||
|---|---|---|
| .. | ||
| minimal-secure-streams | ||
| minimal-secure-streams-alexa | ||
| minimal-secure-streams-avs | ||
| minimal-secure-streams-client-tx | ||
| minimal-secure-streams-proxy | ||
| minimal-secure-streams-seq | ||
| minimal-secure-streams-sink | ||
| README.md | ||
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 |