Fix(core) object store support cn chars #15208
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When configuring N8N to store binary data in S3 (Minio), if the Convert to File node uses a filename containing non-ASCII characters and directly stores it in the S3 metadata without encoding, an error may occur. To avoid this issue, encode the filename using encodeURIComponent before saving it to the S3 metadata. This ensures proper handling of special characters in filenames.
After repair:
Workflow for verification: