Content
View differences
Updated by Markus Kahl almost 7 years ago
Attachments with Unicode filenames (e.g. including Japanese characters) cannot be downloaded via S3. Users will get the following error:
```text
<Error>
<Code> InvalidArgument </ Code>
<Message>
Header value can not be represented using ISO-8859-1.
</ Message>
<ArgumentName> response-content-disposition </ ArgumentName>
<ArgumentValue>
attachment; filename = <something-with-unicode-characters.ext>
</ ArgumentValue>
<RequestId> ... </ RequestId>
<HostId>
...
</ HostId>
</ Error>.
```
This is because S3 does not support anything other than ISO-8859-1 characters for the content disposition value.
```text
<Error>
<Code> InvalidArgument </ Code>
<Message>
Header value can not be represented using ISO-8859-1.
</ Message>
<ArgumentName> response-content-disposition </ ArgumentName>
<ArgumentValue>
attachment; filename = <something-with-unicode-characters.ext>
</ ArgumentValue>
<RequestId> ... </ RequestId>
<HostId>
...
</ HostId>
</ Error>.
```
This is because S3 does not support anything other than ISO-8859-1 characters for the content disposition value.