AWS S3 Plus ('+') sign in path

[bade7n]

I am using user's token to access S3, java sdk version 1.11.521 and reproducible on 1.11.465.

I need to list bucket and read each entry later.

For example object url is https://s3.amazonaws.com/something-dev/dev_files/2017%2B000.zip
While listing something-dev/dev_files everything works fine and I receive object key as
dev_files/2017+000.zip
But

client.getObject(new GetObjectRequest("something-dev", "dev_files/2017+000.zip", null)) 

I got
The request signature we calculated does not match the signature you provided. Check your key and signing method.
Once I encode path to become dev_files/2017%2B000.zip or dev_files/2017%20000.zip or dev_files/2017 000.zip I got The specified key does not exist. (Service: Amazon S3; Status Code: 404.

• I am allowed to use Plus(+) sign as part of file name at all? Because I can't read file in either way and the only solution that comes to my mind is to rename it.
• And if someone managed to read that kind of files - how this sign should be encoded?

Am I missing something?

[debora-ito]

@VladimirIL what version of httpclient are you using?

The SDK should url-encode automatically the param values, you don't have to do any extra encoding.

[bade7n]

Spring boot 2.1.3.RELEASE, aws-sdk 1.11.521, httpclient 4.5.7

[debora-ito]

Could you please try running with httpclient 4.5.5 and see if you still have the same issue?

I reproduced your issue with httpclient 4.5.7, my guess is they introduced some changes in url encoding, we are still figuring out. With httpclient 4.5.5 I don't see the error.

[bade7n]

It works, 4.5.6 works as well. Thanks for a hint.

[bade7n]

It might be cause of number of candidates:
https://issues.apache.org/jira/browse/HTTPCLIENT-1960?jql=project%20%3D%20HTTPCLIENT%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20affectedVersion%20in%20(releasedVersions()%2C%204.5.7)%20AND%20component%20%3D%20%22HttpClient%20(classic)%22

https://issues.apache.org/jira/browse/HTTPCLIENT-1927?jql=project%20%3D%20HTTPCLIENT%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20affectedVersion%20in%20(releasedVersions()%2C%204.5.7)%20AND%20component%20%3D%20%22HttpClient%20(classic)%22

But of course proper investigation is needed.

[debora-ito]

Yes, S3 keys with consecutive slashes // were also impacted by 4.5.7, as reported in #1919.

I'm closing this since we resolved your issue, and you can keep track of the 4.5.7 impact on the other thread. Feel free to reopen if you have any other question.