GNOME Bugzilla – Bug 784703
Rtsp-over-http includes port 80 in internal uri
Last modified: 2018-11-03 11:57:48 UTC
I am having trouble using the rtspsrc for rtsp-over-http that I am starting to think is a bug. Setting protocols and/or setting rtsph does not open a socket to port 80. I am forced to actually put ":80" in the uri. When I do it ends up in the uri posted and the device does not respond. This is contrary to the standard, the device should not see the port 80 in it's url. Multiple devices tested using live555 and curl without issue. Tested with gst-launch on gstreamer 1.12 on windows x64 but primary usage is from c++ program. Is this latest?, I am finding terribly outdated documentation and broken links on https://gstreamer.freedesktop.org/
Where exactly do you find broken/outdated documentation on the website? The latest release is indeed 1.12.1 at this point. It probably makes sense to use port 80 for rtsph by default, but this would break backwards compatibility with any applications that expect it to work like now. Not sure what to do about this here.
Allow me to clarify. According to the documentation on tunneling, the tunneling port is what you connect to but the port should NOT end up inside the rtsp headers. I have verified with other libraries using wireshark that indeed the rtsp headers remain un-udultrated. rtsph seems to actually do nothing. it connects to port 554 rtsph + protocol also seems to do nothing unless a port is specified. This seems odd but is workable. The problem is the rtsp headers are being messed up. rtspsh is not working correctly and I think the same may be true. As for broken/outdated. I need to retract the outdated, I was getting property not supported when I was just spelling it wrong. However the links inside the pages, like https://gstreamer.freedesktop.org/usr/share/gtk-doc/html/gstreamer-1.0gstreamer-GstUriHandler.html#GstURIHandler-struct yield "Not Found". Just an annoyance really, I can google for them separately
Is this tied to 661530 and/or 763313 ?
Looks unrelated to those
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/365.