-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
raw query for the publisher not available in hooks #2483
Comments
Hello, #!/bin/sh
echo $1
echo $2
echo $3
env and i ran it with the configuration you provided: paths:
"~^(some|not-some|test)/(path|other)(.*)":
source: publisher
runOnReady: ./my_script.sh started $G2 $G1 $G3 The script worked correctly and printed the arguments:
and then the entire environment:
So i could not found any bug here. Regarding the possibility of using query parameters in hooks, i'll add an additional environment variable that contains query parameters. Next time please create two separate issues. |
Correct. If streaming to Thanks for #2522 that was exactly what i needed. |
added in v1.2.1 |
This issue is being locked automatically because it has been closed for more than 6 months. |
Which version are you using?
v1.1.1-32-g9de6423
Which operating system are you using?
Describe the issue
We are streaming via RTMP and consuming via HLS. We are using external authentication. RTMP itself starts to stream to rtmp://server.com:1935/some/path?token=xoxo-token
This leads to starting a path called
some/path
When the path is ready to be streamed by clients (HLS) we want to
runOnReady
ascript.sh
which does some internal housekeeping and additional notifications. For this we needquery
to be available in some form (similar toexternalAuthenticationURL
is perfect).Describe how to replicate the issue
ffmpeg -re -i src.flv -c copy -f flv rtmp://server.com:1935/some/path?token=xoxo-token&internal_param=xxx
G3 capture group does not exists. There is also nothing in the env, there are no additional (usable) vars in the invocation of the script
Did you attach the server logs?
no
Did you attach a network dump?
no
The text was updated successfully, but these errors were encountered: