Implement rate limiting based on host ip with python plugin but without auth hook

[Olu]

That’s true, there is still a pending issue Runtime error when calling get_data from Python middleware - #8 by Lohanna_Sarah with the Python get_data API.

The alternative is to use Golang plugin or program a separate connection to Redis then modify the key

@utkarsh079

The issue is that if there is anything wrong with the plugin, all clients start getting 403, which is wrong.
We experienced this recently in production and we had to take the whole tyk implementation away from system. here is the link to that Error with middleware in one gateway while other pods are working fine

Coming back to this, would ensuring one gateway starts before the others not mitigate this?

Also, could you explain more about why you feel a 403 output when there is a plugin error is wrong? My thinking would be if there is a plugin error that is critical to the API request, surely you would want to block authentication and mitigate any kind of security risk. Or would it be the status of the error you are more concerned about?