Andy LoPresto 4f40eca16c

NIFI-3788 Switched Amazon HTTP client instantiation from using null HostnameVerifier (which defaulted to Strict, which cannot handle wildcard certificate hostnames) to DefaultHostnameVerifier, which is fine. ...

I still want to add unit tests and integration tests, but I ran a flow which had previously caused the reproducible exception and this worked fine (flow showed objects were put in S3, no exceptions, and I verified through AWS Web Console that new objects were present).

This closes #1753.

Signed-off-by: Bryan Rosander <brosander@apache.org>

2017-05-04 12:09:52 -04:00

..

nifi-aws-nar

NIFI-3385 - This closes #1440. Updating copyright statements to reflect the new year.

2017-02-16 00:10:02 -05:00

nifi-aws-processors

NIFI-3788 Switched Amazon HTTP client instantiation from using null HostnameVerifier (which defaulted to Strict, which cannot handle wildcard certificate hostnames) to DefaultHostnameVerifier, which is fine.

2017-05-04 12:09:52 -04:00

pom.xml

NIFI-3100-rc2 prepare for next development iteration

2016-11-25 23:49:27 -05:00