Rivka Segan
|
7c0a06b630
|
Clarify that WASM bootstrap uses ws, not wss or DNS
This fixes the logic error of "bootstrapping via TXT record also will
work."
This also adds a clarification that, because DNS is unavailable, the
only option today is ws:// (Veilid currently does not allow wss://
with an IP address. Specifically, try_wss will fail with
apibail_parse_error! and then RPCError::map_protocol.) This
clarification saves time for any users who would otherwise be tempted
to get a certificate for an IP address (at least one free Certificate
Authority supports this, and the resulting certificate can be added
to a veilid-server configuration.)
try_wss failure:
bd4b4233bf/veilid-core/src/network_manager/types/dial_info/mod.rs (L199-L202)
bd4b4233bf/veilid-core/src/rpc_processor/coders/dial_info.rs (L52-L56)
see also:
bd4b4233bf/veilid-core/src/network_manager/types/dial_info/mod.rs (L58-L59)
In addition, several spelling errors are fixed.
|
2023-09-27 05:46:22 +00:00 |
|