Hi;
I'm trying to implement caching of .ts content on the CloudFlare network.
How xtream ui works:
Client 01:
/path1/path2/1_01.ts
Client 01:
/path323/path323/1_01.ts
Instead of all customers accessing the same URL to get the .ts content they access using different URLs.
I don't know if it would be possible to change the structure as Xtream ui works with .ts content.
A solution solution would be for all users to access the .ts content using the same URL but with an authentication token.
Let me know if this is possible or there is another way to make the cache work in CLoudFlare.
my regards.
I'm trying to implement caching of .ts content on the CloudFlare network.
How xtream ui works:
Client 01:
/path1/path2/1_01.ts
Client 01:
/path323/path323/1_01.ts
Instead of all customers accessing the same URL to get the .ts content they access using different URLs.
I don't know if it would be possible to change the structure as Xtream ui works with .ts content.
A solution solution would be for all users to access the .ts content using the same URL but with an authentication token.
Let me know if this is possible or there is another way to make the cache work in CLoudFlare.
my regards.