@itpp, you're right but even if we can partially solve this problem, it'll
be sufficient for us. Well, using below method worked in our case :
location ~ \.(mp4)$ {
mp4;
root /var/www/html/conversion;
expires 1d;
valid_referers servers domain.net content.domain.com ;
if ($invalid_referer) {
return 403;
}
}
This config is only permitting domain.net and domain.com while preventing
any other referer header such as "empty" one.
On Tue, Mar 17, 2015 at 3:38 PM, itpp2012 <nginx-fo...@nginx.us> wrote:
> Which can all be faked (eventually), build some kind of
> validation/authentication system before launching your app.
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,257269,257314#msg-257314
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
