[ 
https://issues.apache.org/jira/browse/NIFI-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dirk Arends updated NIFI-6332:
------------------------------
    Description: 
The PutS3 Processor does not allow you to set the Cache-Control. My use case is 
to put files into S3 to be served and cached via Cloudflare. After looking at 
other issues I found NIFI-2810 which references [Github PR 
1034|[https://github.|https://github.com/apache/nifi/pull/1034] 
[com/apache/nifi/pull/1034|https://github.com/apache/nifi/pull/1034]] which 
added the property Content-Type to PutS3Object.
  
 Would there be anyone who and make these changes.

  was:
The PutS3 Processor does not allow you to set the Cache-Control. My use case is 
to put files into S3 to be served and cached via Cloudflare. After looking at 
other issues I found 
[NIFI-2810|https://issues.apache.org/jira/browse/NIFI-2810] which references 
[Github PR 1034|[https://github.com/apache/nifi/pull/1034]] which added the 
property Content-Type to PutS3Object.
 
Would there be anyone who and make these changes.


> PutS3 Processor adding Cache-Control property 
> ----------------------------------------------
>
>                 Key: NIFI-6332
>                 URL: https://issues.apache.org/jira/browse/NIFI-6332
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.8.0
>            Reporter: Dirk Arends
>            Priority: Major
>
> The PutS3 Processor does not allow you to set the Cache-Control. My use case 
> is to put files into S3 to be served and cached via Cloudflare. After looking 
> at other issues I found NIFI-2810 which references [Github PR 
> 1034|[https://github.|https://github.com/apache/nifi/pull/1034] 
> [com/apache/nifi/pull/1034|https://github.com/apache/nifi/pull/1034]] which 
> added the property Content-Type to PutS3Object.
>   
>  Would there be anyone who and make these changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to