-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrite rules #95
Comments
I think it would make sense to have a header that specifies the path On February 3, 2016 at 8:19:59 AM, elliot nelson ([email protected])
|
Just bumped into the exact same issue, happy to provide a PR if given the direction to fix this. |
+1 |
Worked on a fix for this, you can see it on #137 |
It might be nice to have some facility to provide rewrite rules in a configuration block. For example, if you have some Rack rewrite (or nginx/unicorn-level rewrites), it's difficult to get a signature match.
As an example, if the incoming
request_uri
is/api/v1/posts
, it'd be nice to be able to say:(The desired outcome is that if I POST to
/posts
, and nginx rewrites my request to/api/v1/posts
, ApiAuth will check each possible signature and return true if any of them match.)(Another approach might be an option allowing you to specify a certain header -- Http-X-Original-URI, for example, or whatever header your web server might generate -- instead of using
request_uri
when building and verifying the signature.)The text was updated successfully, but these errors were encountered: