Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/382#discussion_r62359332
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpResponse.java
---
@@ -155,9 +155,9 @@ public void onTrigger(final ProcessContext context,
final ProcessSession session
try {
session.exportTo(flowFile, response.getOutputStream());
response.flushBuffer();
- } catch (final IOException ioe) {
+ } catch (final Exception e) {
--- End diff --
Thinking through this a bit more, catching Exception is probably
appropriate. Typically you want to not blanket catch when creating framework
level code but this needs to be hardened to anything that may happen when
responding.
I am good with how it is now.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
