integration with media-stream-library-js about rtsp-simple-proxy HOT 3 CLOSED

Hello, in my opinion the bug is in media-stream-library-js, and i also found where it is. When an RTSP client contacts a server, this happens:

• the client sends a DESCRIBE request to obtain infos about a stream on a certain path
• the server sends back a SDP document, which describes the stream (how many tracks there are, what is their codec). This document contains, for each track, an URL that is needed to connect to this specific track, that is saved in the control field of the document.

The track URL can be relative, for instance (taken from the RTSP 1.0 specification https://tools.ietf.org/html/rfc2326#appendix-C.2):

a=control:trackID=1

the leading slash is omitted, so if the stream URL is

rtsp://example.com/movie

The resulting track URL is

rtsp://example.com/movie/trackID=1

media-stream-library-js does not insert the leading slash between the absolute URL and the relative URL:
https://github.com/AxisCommunications/media-stream-library-js/blob/master/lib/components/rtsp-session/index.ts#L350

so http://localhost:554/proxyStream/trackID=0 becomes http://localhost:554/proxyStreamtrackID=0.

Try to use http://localhost:554/proxyStream/ as url (with the trailing slash) or edit the library. If it works, we can then send a PR.

from rtsp-simple-proxy.

Hi,

Thank you so much, adding the slash in the javascript did helped !

from rtsp-simple-proxy.

This should be definitively fixed in v0.3.10 - i added a trailing slash to the Content-Base header, so editing media-stream-library-js is not needed anymore.

from rtsp-simple-proxy.