secure urls

[ankurss]

does your current implementation support secure urls ? or can you add this feature ?

example, currently we have different url for each user; this helps us track/restrict users

user 1: http://domain.com/hls/some-secure-code-12345-/chunk1.ts
user 2: http://domain.com/hls/some-secure-code-67890-/chunk1.ts
and so on..

[flavioribeiro]

For now, bemtv associates full URL's with their contents. It doesn't have support for swarm isolation based on the transmission. I'll think about it and get back to you

[flavioribeiro]

hi @ankurss, I don't think this security method is described on the specs. Why are you doing this? It is your segmenter that generates url's like this?

[ankurss]

We need secure url which work only for specific ip range & also needs to expire after few hours.

Segmenter doesn't generate such urls, we are doing internal nginx redirects to achieve such urls.

[flavioribeiro]

I see. You change the master playlist URL also? The swarms are created based on this as you can see in streamroot/clappr-p2phls-plugin#8.

One thing I can do is match segments with their names only instead of full URI. I'm afraid of a adaptive streaming scenario were I can't guarantee that chunks from different levels have different names.

[ankurss]

different levels is indeed a issue, maybe if we added filename+level in url ? and the swarm can use filename-level to find correct chunks

level1: http://domain.com/hls/some-secure-code-12345-/filename-240p/chunk1.ts
level2: http://domain.com/hls/some-secure-code-67890-/filename-360p/chunk1.ts

[flavioribeiro]

Yes, this definitely solves the issue. Can you open a feature request on https://github.com/bemtv/clappr-p2phls-plugin? I'll use this plugin as the base for others.