Thank you! I confirm that with version live.2022.12.01.tar.gz I can receive streams with rtsp-over-https using calls like
openRTSP -T 8881 rtsps://127.0.0.1:12345/whatever where 8881 would be the https port. The port in the url (12345) is meaningless. "rtsps" in the url sounds misleading, but this is my understanding how tls encoding is specified. Thanks again, Johannes On Fri, 2 Dec 2022 11:04:12 +1300 Ross Finlayson <finlay...@live555.com> wrote: > > On Dec 2, 2022, at 9:41 AM, Gajdosik Johannes <j.gajdo...@pke.at> > > wrote: > > > > Hello Ross, > > I am sorry, it is not fixed yet. > > Arggh! Unfortunately I can’t reproduce the exact situation you’re > encountering, so I had to guess the solution, without testing it. > > > Analysis: Here is the modified code in > > RTSPClient::connectionHandler1. ... > > // The connection succeeded. If the connection came about from > > an attempt to set up RTSP-over-HTTP, finish this now: if > > (fHTTPTunnelingConnectionIsPending && !setupHTTPTunneling2()) > > break; > > I think that moving this “if” statement after the other one will fix > the problem. > > Please try the latest version (2022.12.01), and let us know if that > solves your problem. > > > 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 _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
