From 8c13d93bde89e95f484133ef86f93dc1ed5c1934 Mon Sep 17 00:00:00 2001 From: Will Norris Date: Fri, 14 Aug 2015 09:56:47 -0700 Subject: [PATCH] update links to URL Signing wiki page --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d49b6a4..bc23425 100644 --- a/README.md +++ b/README.md @@ -81,7 +81,8 @@ The `s{signature}` option specifies an optional base64 encoded HMAC used to sign the remote URL in the request. The HMAC key used to verify signatures is provided to the imageproxy server on startup. -See [the wiki](https://github.com/willnorris/imageproxy/wiki/URL-signing) for more informations. +See [URL Signing](https://github.com/willnorris/imageproxy/wiki/URL-signing) +for examples of generating signatures. ### Remote URL ### @@ -189,7 +190,7 @@ Reload the [codercat URL][], and you should see an error message. Now load a [signed codercat URL]: http://localhost:8080/500,sXyMwWKIC5JPCtlYOQ2f4yMBTqpjtUsfI67Sp7huXIYY=/https://octodex.github.com/images/codercat.jpg Some simple code samples for generating signatures in various languages can be -found starting in [this comment](https://github.com/willnorris/imageproxy/issues/11#issuecomment-101428470). +found in [URL Signing](https://github.com/willnorris/imageproxy/wiki/URL-signing). If both a whiltelist and signatureKey are specified, requests can match either. In other words, requests that match one of the whitelisted hosts don't