Cannot get secure link with expires to work

Duke Dougal dukedougal at gmail.com
Thu May 2 23:33:01 UTC 2019


>>>>On 1 May 2019, at 10:56 am, Patrick <201904-nginx at jslf.app> wrote:

>>>>On 2019-05-01 10:06, Duke Dougal wrote:

>>>>Any further ideas?


>>>>1) The URL returns 200 when the secure-link config is disabled?

>>>> url="http://127.0.0.1/html/index.html"
>>>> curl -sI $url

>>>>2) The secret, expiry, and uri are the same from md5 generation to the cURL
request?


Yes the URL returns 200 when the secure-link config is disabled.


>> The secret, expiry, and uri are the same from md5 generation to the cURL
request?

Could you please explain the question further? - I’m not sure how to check
this thanks.


On Wed, May 1, 2019 at 10:52 AM Patrick <201904-nginx at jslf.app> wrote:

> On 2019-05-01 10:06, Duke Dougal wrote:
> > Any further ideas?
>
> 1) The URL returns 200 when the secure-link config is disabled?
>
>         url="http://127.0.0.1/html/index.html"
>         curl -sI $url
>
> 2) The secret, expiry, and uri are the same from md5 generation to the
> cURL request?
>
>
> Patrick
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20190503/87a836e3/attachment.html>


More information about the nginx mailing list