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 work. I've been pulling my hair out trying to solve this issue but no one seemsby LewisMM - Nginx Mailing List - English
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 so: http://0.0.0.0:80/video/hls/bunny.m3u8?md5=cAsEEb6J96haWy3CMOSgDg&expires=16by LewisMM - Nginx Mailing List - English
Hi, I've been following this resource: https://www.nginx.com/blog/securing-urls-secure-link-module-nginx-plus/ On that page, the final section "Securing Segment Files with an Expiration Date". It does not work. map $uri $file_name { default none; "~*/s/(?<name>.*).m3u8" $name; "~*/s/(?<name>.*).ts" $name; } server { listby LewisMM - Nginx Mailing List - English
![]() |
![]() |
![]() |
![]() |
![]() |