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

Update client library #6521

Closed
cyberduck opened this issue Jan 31, 2012 · 21 comments
Closed

Update client library #6521

cyberduck opened this issue Jan 31, 2012 · 21 comments
Assignees
Labels
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 31, 2012

Juhieta created the issue

Hi,

I purchased the application from Mac App Store to connect Windows Azure Storage (blob storage).

The Mac App Store version had some problems to connect to Windows Azure, so I installed the latest version from the website (4.2.1).

However, even with this version, when I enter my credentials correctly and try to connect, I get the following error:

##
DNS Error: Connection failed
blob.core.windows.net
##

The problem seems to be that Cyberduck formulates the Azure Storage URL as follows (where MYACCOUNT is my account name):

https://MYACCOUNT@blob.core.windows.net

While it should be:

https://MYACCOUNT.blob.core.windows.net

This completely breaks Azure compatibility of Cyberduck.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 1, 2012

@dkocher commented

The other issue refers to #6468.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 1, 2012

@dkocher commented

This is very much a duplicate of #6246 although the default hostname should possibly be changed. I will have to read up on the Azure documentation.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 1, 2012

Juhieta commented

Ok, hopefully this can be fixed soon!

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 2, 2012

@dkocher commented

Replying to [comment:5 Juhieta]:

Ok, hopefully this can be fixed soon!

Until then the workaround described (enter the hostname manually) should work for you.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 7, 2012

Juhieta commented

Replying to [comment:6 dkocher]:

Replying to [comment:5 Juhieta]:

Ok, hopefully this can be fixed soon!

Until then the workaround described (enter the hostname manually) should work for you.
That would be nice, but I can't find a way to change the hostname manually (not found from the other ticket either). Can you describe the steps to change the full url manually?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 14, 2012

@dkocher commented

Replying to [comment:7 Juhieta]:

Replying to [comment:6 dkocher]:

Replying to [comment:5 Juhieta]:

Ok, hopefully this can be fixed soon!

Until then the workaround described (enter the hostname manually) should work for you.
That would be nice, but I can't find a way to change the hostname manually (not found from the other ticket either). Can you describe the steps to change the full url manually?

This is possible in both the Connection and Bookmark windows.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 25, 2012

Juhieta commented

Replying to [comment:8 dkocher]:

Replying to [comment:7 Juhieta]:

Replying to [comment:6 dkocher]:

Replying to [comment:5 Juhieta]:

Ok, hopefully this can be fixed soon!

Until then the workaround described (enter the hostname manually) should work for you.
That would be nice, but I can't find a way to change the hostname manually (not found from the other ticket either). Can you describe the steps to change the full url manually?

This is possible in both the Connection and Bookmark windows.

Unfortunately it is not possible (or at least I can't find a way how). I'm only unable to change the "Server" (not the final URL).

The orignal problem was:

If I enter to Server field "blob.core.windows.net" and to Username field my Azure account name, the application formulates the URL as:

ACCOUNTNAME@blob.core.windows.net

While it should be:

ACCOUNTNAME.blob.core.windows.net

If I now enter to Server field "ACCOUNTNAME.blob.core.windows.net" and try to leave Username field empty, the application will not allow to connect until I also give the Username. And that will result to:

ACCOUNTNAME@ACCOUNTNAME.blob.core.windows.net

If you really think it should be possible to fix the result URL, could you please give step by step instructions.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 2, 2012

@dkocher commented

Replying to [comment:9 Juhieta]:

I will have to check with my own account. But there should still be a access key that you must use as the username in the login credentials.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 2, 2012

@dkocher commented

We will need to update switch our client library implementation to Windows Azure SDK for Java.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 5, 2012

Juhieta commented

Ok, great to hear that something can be done to fix this!

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 14, 2012

@dkocher commented

#6581 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 10, 2012

Alexey Palazhchenko commented

Looks like there are no workarounds? Small bugfix release maybe? Please.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2012

806c7f0 commented

Replying to [comment:14 Alexey Palazhchenko]:

Looks like there are no workarounds? Small bugfix release maybe? Please.

Same issue here, would really like to use this tool, but connectivity to Azure not working, will likely have to abandon for something else until fix made available.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2013

befde16 commented

+1 for this to be fixed please.

The issue means it is impossible to connect to Azure. (I have just downloaded the Windows version of Cyberduck 4.2.1 and very disappointed.)

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 5, 2013

@dkocher commented

We have removed Azure support completly in e55be0b until we reintroduce support using new API.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 18, 2013

@dkocher commented

Azure protocol support is currently not available.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 23, 2013

f25d034 commented

If you want Azure support brought back to Cyberduck, leave your opinion here.

I definitely want Azure support back.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 28, 2014

@dkocher commented

In 0f967fe.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 30, 2014

@dkocher commented

~~ Enable support in current snapshot builds with setting the hidden property connection.protocol.azure.enable to true

defaults write ch.sudo.cyberduck connection.protocol.azure.enable true

~~

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 30, 2014

@dkocher commented

Download the Azure connection profile to enable Windows Azure Storage support in the current snapshot builds.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 25, 2014

@dkocher commented

Enabled by default in b9638d7.

@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
Projects
None yet
Development

No branches or pull requests

2 participants