2024-04-24, 02:42 AM
(This post was last modified: 2024-04-24, 02:43 AM by AnonymousWebHacker. Edited 1 time in total.)
Just
1 - qos for limit maximum speed at which each IP can access to watch their videos.
or
2 - Nginx and data limit peer user tokeen
When a user is playing a video, every x time an authentication or token verification process is carried out on the server, where the authentication process has a way to catch it. So ?
You can configure nginx to specify that it detects the frame and leaves it valid only for that connection thread, the other accesses to view content, that it has the same token (same user), that it does not allow traffic with transcoded video content, video segmentation , or a raw video, only allowing you access to browse but not play a second time. I would let it play only when the first frame disappears.
1 - qos for limit maximum speed at which each IP can access to watch their videos.
or
2 - Nginx and data limit peer user tokeen
When a user is playing a video, every x time an authentication or token verification process is carried out on the server, where the authentication process has a way to catch it. So ?
You can configure nginx to specify that it detects the frame and leaves it valid only for that connection thread, the other accesses to view content, that it has the same token (same user), that it does not allow traffic with transcoded video content, video segmentation , or a raw video, only allowing you access to browse but not play a second time. I would let it play only when the first frame disappears.