> It is about HTTPS, not HTTP. Sorry, I missed this; I thought that you were referring primarily to HTTP. My apologies.
I might end up adding this functionality sometime in the future. But I’m curious: Does our existing RTSP server implementation support RTSP-over-HTTPS? When I recently added RTSP-over-TLS support to our RTSP server implementation, it wasn’t intended to also support RTSP-over-HTTPS. But perhaps this is working by (happy) accident? Or are you using some other RTSP server implementation to test your modified client? Also, I don’t understand your first proposed patch (changing “fInputSocketNum” to “fOutputSocketNum” in a call to “getsockopt()”). The connection handler function is clearly for handling *incoming* data, so it should always be on the input socket, not the output socket (on which we never receive data). Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
