[ 
https://issues.apache.org/jira/browse/NIFI-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170167#comment-17170167
 ] 

ASF subversion and git services commented on NIFI-7664:
-------------------------------------------------------

Commit ddb304a927b372c518ae84572315f07b75733a28 in nifi's branch 
refs/heads/main from Kent Nguyen
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ddb304a ]

NIFI-7664 Add Content Disposition property to PutS3Object processor

Add new property 'Content Disposition' to allow user
to set the content-disposition http header on the S3 object.

Allowed values are 'inline' (default) and 'attachment'.
If 'attachment' is selected, the filename will be set to the S3 Object key.

Remove default value and keep backward compatibility
Update fetchS3Object filename attribute settin
Update constant names
Update order of if-else condition
NIFI-7664 Update condition in FetchS3Processor
NIFI-7664 Undo the unexpected indent
NIFI-7664 Update international chars unit test
NIFI-7664 Set fetchS3 file path name
NIFI-7664 Update code style

This closes #4423.

Signed-off-by: Peter Turcsanyi <turcsa...@apache.org>


> PutS3 Processor adding Content-Disposition property
> ---------------------------------------------------
>
>                 Key: NIFI-7664
>                 URL: https://issues.apache.org/jira/browse/NIFI-7664
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Dirk Arends
>            Assignee: Kent Nguyen
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The PutS3 Processor does not allow you to set the Content-Disposition header.
> My use case is to be able to control the Content-Disposition header on 
> objects intended to be served via S3 website hosting.
> This is related to NIFI-6332 and both changes can be use NIFI-2810 as an 
> example of how to implement the changes as NIFI-2810 adds the property 
> Content-Type to the PutS3Object.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to