Open cap10morgan opened 8 years ago
We just discovered that query params with location
(or website
or presumably any other signed_subresource string) at the end of the query param name causes this to fail, but otherwise they work. So it seems like the signed_subresource code just needs to ensure that it only grabs query params where the whole string matches, not just a suffix.
Please try the new code on master. This should take care of your issue
I,ve the same problem. I will try to add chop prefix param
We're using this to serve a small JS webapp from S3. Its Javascript code uses a few query parameters, but when we append those to our requests, it results in SignatureDoesNotMatch errors.
An example query param that it has failed on is
foo.html?polling-location
. A request to justfoo.html
succeeds.This is with the latest master HEAD code of this module running in nginx 1.9.3.
Let me know if you need more info to reproduce or diagnose.