Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Discovered this regression while investigate THREESCALE-11741
In PR #1503 we return nil and error in case of an error, however some code paths do not handle the error but instead check the error field of the response object and lead to unexpected behavior (bypass backend-listener authrep call).
The return value of http_ng backends is also inconsistent, some backends return errors while others return response objects with error fields. This leads to some code paths checking for errors (always nil for resty backends) while others check the response object for errors or ignore errors altogether. This needs to be investigated
Verification steps
docker-compose.yml
as followYou should get HTTP/1.1 403 Forbidden