Unexpected behavior of rate-limiting plugin with path option

[nvervelle]

Hi everyone,

I'm trying to use the rate-limiting plugin with path option because I want to limit the frequency of calls on one specific endpoint among the other endpoints in the same ingress. I was hoping that the path option of the rate-limiting plugin would work, but it doesn't.

The problem I see is that the plugin applies limits even to other paths than the one explicitly specified, so it seems rather useless to me that way.

I think this behavior is due to the method get_identifier in handler.lua : if the request path is different than the configured path, then it ends up returning the forwarded IP as the identifier, hence triggering a rate limiting on the forwarded IP.

For me, it seems to be a bug, do you agree ?
If you agree that it's a bug, do you want me to open a PR to change this ?
If you think it's normal behavior, can I suggest a PR to add an option to handle this ?

[nvervelle]

I found this issue that seems related : #10672

And this other discussion : #7404