-
Notifications
You must be signed in to change notification settings - Fork 17
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
Support within limit_except
- is it possible?
#16
Comments
Using it like this fails with
is this a hard-coded limitation? Is it implemented in open-source nginx like this? Is their commercial |
I raised an issue in nginx nginx/nginx#368 for a more generic solution to |
I wonder if I should add NGX_HTTP_LMT_CONF to Configuration Directives.
I haven't tested it yet, but it seems to pass the test configuration by adding it. |
Looks promising! It seems that there are no specific reasons for why the other auth types are simply not available within this block?! |
bb676de: add limit_except to the following directive context
|
thank you very much - very nice! I will have to wait for it becoming part of the alpine release though to fully roll it out! |
Create a new version and request an update of the alpine package |
I'm sorry @kjdev is this a question or a statement? Can I do this, or help you with it? |
Statement. |
According to the nginx documentation, their version of the jwt auth as delivered with the commercial subscription is usable within the
limit_except
configuration part.This is very useful, if for example, I want to generally allow GET request, but want to limit PUT requests, which would be configured like this
is this module capable of being used this way?
The text was updated successfully, but these errors were encountered: