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
I'm using mediamtx as a middleman for loading an RTSP stream into my react frontend.
I'm using my own backend as an external authentication server.
It expects to receive a token in the query field of the payload.
Reading and writing should be in this format. Some/Extended/Path?token=SecretToken
The problem
I can publish an RTSP stream fine using ffmpeg with the token, but I can't read it again with WebRTC.
When I unmarshal the payload in my backend, I can see that the query field is an empty string.
I've found that it works with release v1.2.1, and breaks with v1.3.0.
The only difference I can see in the logs, is that with v1.3.0, the token seems to disappear after the server makes a 301 redirection.
And for some reason, it transforms my path into Some/Extended/Some/Extended/Path from Some/Extended/Path, but I'm guessing this is just a formatting change.
Let me know if you need more information.
Describe how to replicate the issue
configure server to use external authentication server
start external authentication server, that accepts token in query from payload
start the mediamtx
publish with ffmpeg with a token as a query parameter (works)
read with webrtc with a token as a query parameter (fails)
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?
v1.2.1 and v1.3.0
Which operating system are you using?
Describe the issue
My setup
I'm using mediamtx as a middleman for loading an RTSP stream into my react frontend.
I'm using my own backend as an external authentication server.
It expects to receive a token in the
query
field of the payload.Reading and writing should be in this format.
Some/Extended/Path?token=SecretToken
The problem
I can publish an RTSP stream fine using ffmpeg with the token, but I can't read it again with WebRTC.
When I unmarshal the payload in my backend, I can see that the
query
field is an empty string.I've found that it works with release v1.2.1, and breaks with v1.3.0.
The only difference I can see in the logs, is that with v1.3.0, the token seems to disappear after the server makes a 301 redirection.
And for some reason, it transforms my path into
Some/Extended/Some/Extended/Path
fromSome/Extended/Path
, but I'm guessing this is just a formatting change.Let me know if you need more information.
Describe how to replicate the issue
Did you attach the server logs?
yes
v1.2.1 logs
v.1.3.0 logs
Did you attach a network dump?
no
The text was updated successfully, but these errors were encountered: