-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
WebRTC: HTTP Callback unable to authenticate by special chars #2774
Comments
The version is too old, try upgrading to the latest version.
|
Should we directly pull the b0 or pull the 4.0 release code and recompile it in Docker? Can we merge h265?
|
Tested and confirmed effective SRS/4.0.201 [2021-12-08 03:18:25.149][Trace][1][999t5o91] TCP: before dispose resource(HttpConn)(0x3ed2730), conns=26, zombies=0, ign=0, inz=0, ind=0
|
The handling of RTC callback information seems to have occasional issues. The actual properties for Stream and App should be maintained. {"Action":"on_play","Client_Id":"754z4331","IP":"127.0.0.1","Vhost":"defaultVhost","App":"live/ID0602181091342360960853","Stream":"aEQJIgUB","Param":"?token=3LUOEAwOpObmRGS/oJoZ353NFB4hEGvnfFC+hXUEiYUy1rNTPZv2kzxoQGdreqUxQ2LAqH7jLi6daBoYz10ald9","Send_bytes":null,"Recv_bytes":null,"TcUrl":null,"PageUrl":"","Cwd":null,"File":null} The actual properties should be:
|
3LUOEAwOpObmRGS/oJoZ353NFB4hEGvnfFC+hXUEiYUy1rNTPZv2kzxoQGdreqUxQ2LAqH7jLi6daBoYz10ald9
|
webrtc://127.0.0.1/live/ID0602181091342271250873?token=IZOLadRRLwfqPw+Lgj8au8DYaeID20yhsMJdrXEr5NmAqKZPEr+7kLGNjE3xnlgiBLWIJqPcGA9rx6emCPhrQcPAOsd8sT6d [2021-12-08 06:09:09.018][Warn][1][6831u6vd][0] RTC error code=3008 : RTC: http_hooks_on_play : on_play http://192.168.0.11:5000/api/v1/StreamServer/OnCallBack : http: on_play failed, client_id=6831u6vd, url=http://192.168.0.11:5000/api/v1/StreamServer/OnCallBack, request={"server_id":"vid-1h15295","action":"on_play","client_id":"6831u6vd","ip":"223.83.155.124","vhost":"defaultVhost","app":"live/ID0602181091342361170874","stream":"WhoXeDmxQxqDukIutEXI6FQ0psXdBSXQWDdTQ99dY","param":"?token=0emw+WhUdoKA8YyV9FPIGqa4dvOj/K0/5sIk2RqXrvTRVobZOHVcxm","pageUrl":""}, response=1, status=200 : http: response number code 1 |
The token generated by PKCS may contain slashes ("/"). The actual behavior of the streaming media service may mistakenly truncate the slashes ("/"), but the mainstream token generation method is PKCS...
|
That is a compatibility issue with the format.
|
Indeed
|
This requires encoding the QueryString, a simple way to bypass it is to URL encode and give it to SRS. A better approach is to encode the URL when SRS callback occurs, referring to the handling in JS or Go.
|
Description
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: