On 23/06/2021 20:23, Weston Schmidt wrote: > 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
The client here is cURL (so under our control), and the server never sees the scheme in this scenario so isn't relevant. Cheers ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
