[NIFI-6122] PutS3Object should support national characters in filenames

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.10.0, 1.9.2
• Component/s: Extensions
• Assignee: Peter Turcsanyi
• Reporter: Peter Turcsanyi
• Created: 14/Mar/19 15:00
• Updated: 15/Jun/22 16:53
• Resolved: 20/Mar/19 01:54

Description

PutS3Object sends the filename in the Content-Disposition HTTP header to S3.
If the filename contains national characters, then the encoding will be wrong which results in the following error:

com.amazonaws.services.s3.model.AmazonS3Exception: The request signature we calculated does not match the signature you provided.

(Due to the character encoding error, the S3 client and the server calculate the signature based on different byte sequences.)

The filename should be URL encoded before sending to S3.

Issue Links

• is related to: NIFI-10105 FetchS3Object does not decode encoded Content Disposition header
• links to: GitHub Pull Request #3373