mirror of
https://libwebsockets.org/repo/libwebsockets
synced 2024-12-04 13:57:15 +00:00
91c6667c04
Just like there is a default protocol provided if none is specified that is suitable for handling http GET, introduce a default SS policy that is also suitable for the case of http GET where the user trusts the CA using the ssl library or system trust store.
27 lines
868 B
Markdown
27 lines
868 B
Markdown
# Secure Streams
|
|
|
|
## Default Secure Streams policy
|
|
|
|
Similar to how low-level lws provides a default protocol
|
|
suitable for the common case of http processing that is
|
|
available is no explicit user protocol is provided, SS
|
|
provides a simple default policy that is suitable for
|
|
https connections that are trusted by the system trust
|
|
store.
|
|
|
|
This typically requires:
|
|
|
|
1) Openssl, which is wired up to a trust store
|
|
2) Http GET type connections on :443
|
|
|
|
If you need anything more complicated, you will have to
|
|
provide your own policy JSON in place of the default one.
|
|
|
|
The default policy defines a streamtype "__default" that
|
|
allows overriding `${endpoint}` with metadata. What you
|
|
put here may be just the endpoint address like `mysite.com`,
|
|
or it can be a url like `https://mysite.com:1234/path`,
|
|
the elements given here control the stream address, port and
|
|
url path.
|
|
|