Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/398
Actually, I think the Response#priorResponse probably doesn't apply to our
case after thinking about it a bit more. The key way to avoid the issues seen
is a flag/counter within that authenticator to track if an attempt to
authenticate has been made and then throw an exception in that case. I think
the handling is fine now, but we can bypass the HTTP client's internal retries.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
