Support for ws(s):// appears to depend on both the client and server handling the scheme. I'd imagine if we chose some reasonable defaults like wss:// implies websocket and provide the ability to request that an https:// be handled as a websocket via a CURLOPT that might make it easy to use.
Wes On Wed, Jun 23, 2021 at 8:46 AM Tomalak Geret'kal via curl-library <curl-library@cool.haxx.se> wrote: > > On 23/06/2021 16:38, Henrik Holst via curl-library wrote: > > Would it not be better to use the normal URI used for > > Websockets which are "ws(s)://" instead of the http(s) or > > am I missing something? > > Yes, this. > > Cheers > ------------------------------------------------------------------- > Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library > Etiquette: https://curl.se/mail/etiquette.html ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
