> That’s what I thought. I may add support for client-side RTSP-over-HTTPS sometime in the future, but (in order to
test this properly) I won’t do so until I also implement this in our RTSP server.
I fully understand that you need some kind of reference implementation on the
server side.
At the
> Simple and unsuccessful beats complicated and successful?
Of course, not.
However, for the tests I needed, the socat "tricks" proved to be simple and
successful.
I would like to stress that it is about tests, not a production quality
solution.
I just needed RTSP sources with different transpor
> Did you try stunnel or nginx as the HTTP to HTTPS proxy? Those are more likely to implement the wide array of TLS
functionality your end devices require than the more limited socat.
I successfully used stunnel, and possibly tried traefik and caddy, but it was
some weeks ago.
I also considered
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?
I don't think so, but I have to admit, I was mainly interested in the client
side, so I haven't checked it extensively.
When I recently adde
(For whatever reason, the mails are not delivered to my mailbox /yet?/,
even though I did not set digest mode, so the thread won't be nicely formatted.)
Huh? RTSP-over-HTTP on the client side has been implemented for more than 17
years now. This already works. Just pass a (non-zero) value fo
Hi Ross,
I made an attempt at implementing RTSP over HTTPS tunneling on the client side.
I've split the changes into 3 patch sets.
I tried to use tabs and spaces that match the surrounding code. In order to
keep the tabs,
I attached the patches instead of pasting them into the mail body.
1. The
