Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS S3 Browser fails when path contains "//" #11715

Closed
cyberduck opened this issue Jun 25, 2021 · 2 comments
Closed

AWS S3 Browser fails when path contains "//" #11715

cyberduck opened this issue Jun 25, 2021 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 25, 2021

f9667e8 created the issue

When a path contains two delimiters without text between them the browser fails. AWS specifically allows this pattern so it should be supported. Simply treat as a directory with no name.

To reproduce

  1. Upload a file to an s3 bucket with the path hello/world//today.txt
  2. Attempt to browse to the file within Cyberduck.
  3. Upon selecting the "world" directory the error states "file not found! contact your host."

Workaround:
I was able to navigate to the directory using S3 Browser and the AWS S3 web interface successfully and update the path.

This is a common typo/error in when writing files via programming code so a fix would be welcome to help debug these kinds of mistakes.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 25, 2021

f9667e8 commented

wiki format seems to be breaking my example the path should say "hello/world/ /today.txt" without the space between "world/" and "/today".

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 25, 2021

@dkocher commented

Duplicate for #10981.

Loading

@cyberduck cyberduck closed this Jun 25, 2021
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants