You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2021/05/18 17:02:03 I [0/0] rtsp-simple-server v0.16.0
2021/05/18 17:02:03 I [0/0] [RTSP] TCP listener opened on :8554
2021/05/18 17:02:03 I [0/0] [HLS] listener opened on :8888
2021/05/18 17:02:03 I [0/0] [path test/path] [rtsp source] started
2021/05/18 17:02:03 I [0/0] [path test/path] [rtsp source] ready
2021/05/18 17:02:08 I [0/0] [HLS] [conn 172.18.0.1:63864] GET /test/path
2021/05/18 17:02:08 I [0/0] [HLS] [converter test] opened
2021/05/18 17:02:08 I [0/0] [HLS] [converter test] ERR: unable to find a valid configuration for path 'test'
2021/05/18 17:02:08 I [0/0] [HLS] [converter test] closed
Slashes are perfectly legal characters for url paths, and it works fine with RTSP, but fails with HLS.
I suppose the reason is that the HLS converter / server does not properly handle nested directories for the stream fragment files.
Theoretically, as far as the server is concerned, it is easy to work around by replacing slashes with dashes for example, but from a system integration point of view it's a lot of work for me, to maintain backwards compatibility as the path is shared with RTSP.
Please let me know if it's possible to fix it, so I can wait for the upgrade, otherwise I will apply the workaround.
The text was updated successfully, but these errors were encountered:
This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.
Which version are you using?
v0.16.0
Which operating system are you using?
OS
Architecture
Describe the issue
config.yaml
Slashes are perfectly legal characters for url paths, and it works fine with RTSP, but fails with HLS.
I suppose the reason is that the HLS converter / server does not properly handle nested directories for the stream fragment files.
Theoretically, as far as the server is concerned, it is easy to work around by replacing slashes with dashes for example, but from a system integration point of view it's a lot of work for me, to maintain backwards compatibility as the path is shared with RTSP.
Please let me know if it's possible to fix it, so I can wait for the upgrade, otherwise I will apply the workaround.
The text was updated successfully, but these errors were encountered: