Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/398
@pvillard31 Sounds fair. Will get this incorporated. Thanks for the
contribution.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/398
Yep, not sure it's worth it. I think it is fine to let the PR as is.
---
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
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
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/398
Hey @apiri,
Many thanks for the review!
Regarding HTTPS, at the time I submitted the PR I was testing it with
CCProxy (on Windows computer). I can't test it again with this setup
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/398
Hey @pvillard31,
I did a review of this and it seems to work mostly well using Squid with
the following config:
```
auth_param basic program
