Unify native and web client connection string #1135
Labels
enhancement
New feature or request
topic:networking
Networking, including protocol and transmission medium
topic:web
Related to running on the Web
Currently native client expects either:
Web client always expects an https URL of a form “https://SERVER:PORT” and it has special handling for our ensure-running API.
Could we make them consistent by making web client accept the same as native one?
The text was updated successfully, but these errors were encountered: