You may have cause to protect certain content on your site, but do not want to integrate full user authentication to allow access to that content. One way of enabling this is to use NGINX's
secure_link module. By passing configure the
--with-http_secure_link switch at compile time, you get access to the
secure_link_secret directive, and its corresponding variable
secure_link module works by computing the MD5 hash of a link concatenated with a secret word. If the hash matches that found in the URI, then the
$secure_link variable is set to the portion of the URI after the hash. If there is no match, then
$secure_link is set to the empty string.
One possible scenario is to generate a page of download links using ...