When we use Special characters in s3 folder and files. They are not resolved S3FileNameParser fails to get the URI. Have seen in the code we are just replacing space with its special character. However if we see the S3 file name creation mechanism they are encoding all name and then replacing special characters with appropriate things like URLEncoder.encode(basePath, "UTF-8").replace("%3A", ":").replace("%2F", "/").replace("+", "%20"); Instead of just replacing the space if we add this line before creating the URI this problem will be resolved.
I have forked the branch should I commit the change ? and what is the process of getting the new release as its urgent for me. This issue is related to this one. https://github.com/abashev/vfs-s3/issues/60
When we use Special characters in s3 folder and files. They are not resolved S3FileNameParser fails to get the URI. Have seen in the code we are just replacing space with its special character. However if we see the S3 file name creation mechanism they are encoding all name and then replacing special characters with appropriate things like URLEncoder.encode(basePath, "UTF-8").replace("%3A", ":").replace("%2F", "/").replace("+", "%20"); Instead of just replacing the space if we add this line before creating the URI this problem will be resolved.
I have forked the branch should I commit the change ? and what is the process of getting the new release as its urgent for me. This issue is related to this one. https://github.com/abashev/vfs-s3/issues/60