Folder slash not correctly shown about s3-signed-url

[rbrigham]

The forward slash is URL encoded to %2F. That should work in a browser or other HTTP clients. Let me know if there's a particular client that the URL wont work in.

For example, it does not work on Google Chrome.

Well, the request work, but that is wrong request, as the name of object has been changed, right? The object is not any more /new/tgbai.txt but it is new%252Ftgbai.txt so it cannot be the same.

[rbrigham]

While it looks different on the surface, both represent the same URL. There's a wiki article on URL encoding at http://en.wikipedia.org/wiki/Percent-encoding that can provide more background. Special characters are often encoded because they can cause confusion to other parsing systems when they use the same characters as delimiters.

Why don't you try it out yourself on the URL you just gave me:
http://en.wikipedia.org/wiki/Percent-encoding is simply not the same as:
http://en.wikipedia.org/wiki%2FPercent-encoding

My question is not how it should be, I would like to know, if you can repair this script that it gives correct URLs. As otherwise signed URLs, do not give the objects! They are not accessible, provided the object is in the folder. So, something is wrong.

I see, signed URL gives the object on Amazon directly, but if I use VANITY, on my bucket, it does not. Maybe it is my mistake with my permissions. Still, it would be nice, if you have clear URLs in this script with slash instead with %2F -- I understand about URL encoding, but can that be an option in the script? Instead of forcing it?

[rbrigham]

Nope not your mistake. It seems there's a problem in the underlying Perl module I'm using to generate the signed URLs when you use the vanity format. I'm investigating a little further to see if there's a workaround/fix.

[rbrigham]

It looks like the encoded path in the URL will work with the VANITY format, at least in my testing. It would look better with the unencoded slash though. I'll reopen to track as a feature request, but I haven't touched this project in a while. I'm very open to pull requests though. :)

[rbrigham]

I added a --no-encode switch to disable escaping the object key if desired.

Thanks!