-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MTX_QUERY not being passed when using WebRTC runOnDemand #4138
Comments
This might be related to #3937 |
aler9
added a commit
that referenced
this issue
Jan 11, 2025
Thanks for reporting the issue, this is fixed by #4141 |
aler9
added a commit
that referenced
this issue
Jan 11, 2025
aler9
added a commit
that referenced
this issue
Jan 11, 2025
aler9
added a commit
that referenced
this issue
Jan 11, 2025
aler9
added a commit
that referenced
this issue
Jan 11, 2025
aler9
added a commit
that referenced
this issue
Jan 11, 2025
Thank you @aler9 - you are fast! |
This issue is mentioned in release v1.11.1 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which version are you using?
1.10.0
Which operating system are you using?
Linux amd64 standard
Describe how to replicate the issue
add a runOnDemand script such as below
`https://localhost:8889/mystream?q=hello
I tested this on chrome, safari, etc.
If you connect to the server using RTSP such as rtsp://localhost:8554/mystream?q=hello you WILL get MTX_QUERY. So I think this is just isolated to WebRTC
Thanks
Server logs
No response
Network dump
No response
The text was updated successfully, but these errors were encountered: