-
-
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
2.0.243 HTTP API has not been tracking clients playing HLS. #996
Comments
hls, due to the multiple requests of m3u8 and ts, is different from the long connection of rtmp and flv protocols. It is estimated that it is not possible to count the number.
|
I'm not very familiar with the HTTP protocol. Is there a field that corresponds to each client? If so, I can do the statistics myself.
|
That requires the client to pass the session parameter, which is theoretically feasible. However, it requires cooperation from the client for development.
|
If HLS is distributed through a regular HTTP server, it will not associate m3u8 and ts files, so the connection count is unknown. SRS3 can do this and improve the statistical information.
|
SRS can act as an HLS origin server. When a client accesses it, for example, The requirement is for the HTTP edge server to return a 302 status code to the client, instead of directly following the 302 redirection.
|
This matter should be done at the edge, because if it is done at the origin server, each piece will have to be returned to the source, losing the function of HTTP edge.
|
It may be done in SRS4. After enhancing the HTTP capability, it may be possible to track the number of HLS clients.
|
|
See #1657 |
Dup to #1657 |
The RMTP client can provide statistics.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: