API: Secure HTTP API for Authentication. Port 1985 does not have any security authentication. #1640
Description
Description'
Please ensure that the markdown structure is maintained.
Currently, the program is used to kick out timed-out streaming clients through the API. However, it has been observed that anyone with a basic understanding of SRS can view and even kick out legitimate clients. Is there any way to avoid this issue?
I saw a post earlier that mentioned listening to port 1985 on 127.0.0.1 and then using another HTTP proxy to achieve this. Could you please explain how to implement the above method in a Docker deployment environment?
- SRS version:
v3 - Deployment method: k8s
TRANS_BY_GPT3