FYI issues when [ or ] is in file or folder name

[scottdunnflux]

My bucket contains folders whose name contains both a [ and a ]

While browsing the bucket the following is fine
http://s3auth.example.com/AMCopyObjects/September%202016_6824718/Well_64/

But we get an error when clicking on a folder on that page that uses the following uri:
http://s3auth.example.com/AMCopyObjects/September%202016_6824718/Well_64/Layout%20[Print]_7348007/index.html

Error message is:
request URI is not encoded correctly: java.net.URISyntaxException: Illegal character in path at index 57: /AMCopyObjects/September%202016_6824718/Well_64/Layout%20[Print]_7348007/index.html
It stops there but I think it would choke at 63 as well.

According to my research the URI should be something like
/AMCopyObjects/September%202016_6824718/Well_64/Layout%20%5BPrint%5D_7348007/index.html

[davvd]

@yegor256 please dispatch this issue

[scottdunnflux]

And, as long as we're talking about URI encoding issues, check for cases where file names include a semicolon
This doesn't produce the same error, but the URI is improperly formed.
In my case s3auth shows something like
http://amk4s3.aws.fluxconsulting.com/AMK4Export/July_August%202014_2406031/Layout%20_Print__7348007/0714_WEL_Yager_Creative_3667028/0714_WEL_Yager_CreativeProces_3667028;63.indd.gz
when it should show %3B for the ;

[yegor256]

@scottdunnflux good question... we're just using the URI provided as is. This means that you have to encode everything before giving us the URI. We don't touch it, we just send it to AWS "as is". Or I didn't understand the problem?

[scottdunnflux]

We're not sending any URLs to the S3 bucket, only files and folders...

Here's an example of the URL I'm seeing at AWS:

And here's the source html of the s3auth page that shows the same file where the URL is different.

This is page is auto-generated by s3auth.com

prefix: NJDK4Export/January 21, 2015_2746522/Layout_3692634/0121LAYOUT p7 grain_2776738/

Name	Size (bytes)
NJDK4Export/January 21, 2015_2746522/Layout_3692634/0121LAYOUT p7 grain_2776738/0121 grain_2776959_6/
NJDK4Export/January 21, 2015_2746522/Layout_3692634/0121LAYOUT p7 grain_2776738/0121LAYOUT p7 grain_2776738;4.indd.gz	3918628

[scottdunnflux]

Looks like that source didn't make it as intended, but you can still see how the URL comes across through s3auth.

[yegor256]

@scottdunnflux I'm sorry this bug is still not fixed. We didn't have enough funds/time to work on the project. However, recently we received some donations from our grateful users and will continue to fix issues and introduce new features. Would be great if you can also donate -- to help us move forward faster. Here is the link: https://www.0crat.com/contrib/C3RP1J1CH