[ https://issues.apache.org/jira/browse/NIFI-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590817#comment-16590817 ]
James Srinivasan commented on NIFI-830: --------------------------------------- Should Content-Disposition also be considered? As already noted, this will definitely break backwards compatibility (I can think of at least one case in our operational flows) > For GET requests, InvokeHTTP should set the filename of the 'Response' > FlowFile based on the URL > ------------------------------------------------------------------------------------------------ > > Key: NIFI-830 > URL: https://issues.apache.org/jira/browse/NIFI-830 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions > Reporter: Mark Payne > Priority: Minor > Labels: beginner, newbie > Attachments: > 0001-NIFI-830-core-attribute-flowfileName-will-be-last-se.patch > > > When using InvokeHTTP to fetch the content of a particular URL, I expected > that the filename of the 'Response' FlowFile would be set to the filename > pulled. I.e., if I pulled http://www.somesite.com/images/1.png, I would have > expected the 'Response' FlowFile to have a filename of "1.png" but instead it > had the same filename as the incoming FlowFile. > I don't think this is something that we can change until version 1.0.0 > because it could potentially break backward compatibility of flows by > changing the filename unexpectedly. In the meantime, I have added an > UpdateAttribute to set the filename to > ${url:substringAfterLast('/'):substringBefore('?')} -- This message was sent by Atlassian JIRA (v7.6.3#76005)