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

Interoperability with FireUploader #6123

Closed
cyberduck opened this issue Aug 1, 2011 · 2 comments
Closed

Interoperability with FireUploader #6123

cyberduck opened this issue Aug 1, 2011 · 2 comments
Assignees
Labels
bug cloudfiles Rackspace CloudFiles thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

Andrew0204 created the issue

When I make new folders within a Cloudfiles container using Cyberduck, the folders it creates are reported by the Rackspace CloudFiles Manager as being of type application/directory. I have been using FireUploader for Firefox for a long time now and have created many folders within containers for my websites and these folders are reported by the Rackspace Cloudfiles Manager as type application/folder. The problem is that all my existing folders within containers that I have created with FireUploader can't be viewed or opened in Cyberduck - it doesn't recognize them as folders. In fact, the Cyberduck info box reports the folders as Kind:Unknown.

And, the reverse causes a problem too. If I create a folder within a CDN container using Cyberduck, the file type application/directory, is not recognized by FireUploader and can't be opened.

Would it be possible to provide CloudFiles options in Cyberduck so that the file type can be set to either application/folder or application directory when creating or viewing folders within containers?

At the moment this problem is preventing me from using Cyberduck, which is disappointing because I find it easier to use than FireUploader.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We follow the recommendations of the Rackspace developer documentation about setting a proper MIME type for directory placeholders. Others should do the same.

@cyberduck
Copy link
Collaborator Author

Andrew0204 commented

Ok, thanks anyway.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug cloudfiles Rackspace CloudFiles thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

2 participants