-
-
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
Redirected flow name duplicated in the origin server cluster #1575
Comments
Add an edge on top of this, push to A and B, both edges can play normally, but I see in #464 (comment) that there is an example of what I mentioned above, and this example cannot run.
|
First of all, the quality of this issue is very high. It can directly reproduce the problem following your steps. The description is clear, logical, and reasonable. I give you 5 thumbs up. 👍👍👍👍👍 Furthermore, regarding this issue, the actual returned URL is a complete RTMP URL stream address (as shown in the figure below), but the redirect of "srs-player" is used as the tcURL and not a complete RTMP URL. Then, it adds an additional streamName: Please make sure to maintain the markdown structure.
Referring to the definition of RTMP in FMS, it is actually the tcURL and not a complete RTMP URL. You can refer to this link for more information: #369 (comment) Please make sure to maintain the markdown structure. So, in the end, it is still a problem of redirection. It should only return the tcUrl instead of the complete RTMP URL. Please make sure to maintain the markdown structure.
|
Explain why the redirect address of FMS is tcUrl instead of RTMP URL, because RTMP is divided into connect(tcUrl) and play(streamName), which means that the RTMP URL is divided into two stages. Generally, the redirect will be in onConnect, for example:
During onConnect, only the tcUrl should be redirected, as there is no streamName at this point.
|
Solution:
Please make sure to maintain the markdown structure. While maintaining compatibility, try to align with the HTTP URL as much as possible. Please make sure to maintain the markdown structure. srs-player is working fine, edge is normal.' Please make sure to maintain the markdown structure.
|
Repeated redirection flow name in the origin server cluster
3.0-a8
Replay
How to replay bug?
Docker configuration file
origin-a.conf
origin-b.conf
origin-a
andorigin-b
and set them to cluster with each other by listening on the HTTP API port.origin-a
.push rtmp://192.168.31.131/streams/123
origin-a
, it works fine, but when usingorigin-b
, it cannot play and returns a 302 error with the stream name repeated.ffplay rtmp://192.168.31.131:1935/streams/123 ok
ffplay rtmp://192.168.31.131:1936/streams/123 get 302 to rtmp://192.168.31.131:1935/streams/123/123
SRS Console Complete Information
Expected Behavior (Expect)
The expected return should be
rtmp://192.168.31.131:1935/streams/123
.I have been looking at this feature for a long time, and there are no other related issues. Did I misunderstand something?
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: