On Wed, Aug 31, 2022 at 05:42:27PM -0400, LewisMM wrote:
Hi there,
> I make a request with the .m3u8 file with the MD5 Hash and expiration. It
> receives a 200 code. Then the m3u8 playlist file tries to load the first
> segment in the playlist, however, I receive 403 "Not Authorised" error.
> Ngi
Hi Paulo,
Very confused by the wording in the link I posted (my first post in this
thread):
"Here’s another example of a secured URL with expiration date, used to
protect both the playlist for a media asset and the segment files."
Which implies it is in fact possible, but alas the code does not
Hi there,
As far as I know, you need to modify your m3u8 files to include the *hash*
and *expire* on every .ts segment. I used to stream HLS using the secure
link module and I remember needing to rewrite the files on-the-fly to make
them include those.
Nginx will not automatically generate a m3u8
Hi,
I make a request with the .m3u8 file with the MD5 Hash and expiration. It
receives a 200 code. Then the m3u8 playlist file tries to load the first
segment in the playlist, however, I receive 403 "Not Authorised" error.
Nginx isn't passing the MD5 hash and expiration to the segment file.
Like
On Wed, Aug 31, 2022 at 11:16:23AM -0400, LewisMM wrote:
Hi there,
> I've been following this resource:
> https://www.nginx.com/blog/securing-urls-secure-link-module-nginx-plus/
> This works with the .M3U8 playlist file. It successfully secures it.
> However, when the playlist tries to load the
