[Bug 753583] New:=?UTF-8?Q?=20RTSP=20Server=20sends=20Not=20Found=C2=A0error=20if=20mount=20point=20is=20set=20to=20?="/"

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=753583

            Bug ID: 753583
           Summary: RTSP Server sends Not Found error if mount point is
                    set to "/"
    Classification: Platform
           Product: GStreamer
           Version: 1.4.5
                OS: Linux
            Status: NEW
          Severity: minor
          Priority: Normal
         Component: gst-rtsp-server
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: marcin at saepia.net
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

The following piece of code (Vala)

rtsp_factory = new Gst.RTSPServer.MediaFactory();
rtsp_factory.set_launch(pipeline_description);
rtsp_factory.set_shared(true);
rtsp_server.get_mount_points().add_factory("/", rtsp_factory);

Will cause Not Found error in the client

vagrant at trusty64:/vagrant$ gst-launch-1.0 playbin uri=rtsp://example.com:6000/
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://plumber1.stag.srv.radiokit.org:6000/
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
ERROR: from element
/GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstRTSPSrc:source: Could not
write to resource.
Additional debug info:
gstrtspsrc.c(6450): gst_rtspsrc_setup_streams ():
/GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstRTSPSrc:source:
Error (404): Not Found

In the debug info at the server the following information appears:

0:00:24.850234488  4980       0xd22540 ERROR             rtspclient
rtsp-client.c:641:find_media: client 0xd588b0: no factory for path /stream=0
0:00:24.850375091  4980       0xd22540 ERROR             rtspclient
rtsp-client.c:1993:handle_setup_request: client 0xd588b0: media '/stream=0' not
found

The issue does not happen if mountpoint is set to "/something" instead of "/".
It seems that there's a fault in function that extracts mount point name from
media URI.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.