Description of problem: cyberduck not working with present swift-plugin, for windows as well as for mac. Investigating the issue Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Assigning it to myself, for further investigation.
I have tried to debug the problem and the issue happening is that GET call made from cyberduck results with an error, HTTP/1.0, 412 --- means precondition failed, the problem happening is that in the logs we are finding only /v1.0 being appended not auth/v1.0, "Dec 22 09:24:58 RHSSA1 proxy-server 172.19.1.25 172.19.1.25 22/Dec/2011/09/24/58 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.1%20%28Mac%20OS%20X/10.6.8%29%20%28i386%29 - - - - - - 0.0002" tried to add the similar strings via cyberduck gui's "more options" still the failure is same from mac and windows both. Other point, as the documentation I have gone through for cyberduck with openstack http://trac.cyberduck.ch/wiki/help/en/howto/openstack does not talk about usage with "tempauth".
with 4.0.2 the windows is responding with "Unexpected Problem, probably in parsing Server XML" whereas swift-plugin reports back mentioning, Dec 26 06:35:43 RHSSA1 proxy-server - 10.1.12.19 26/Dec/2011/06/35/43 GET /auth/v1.0 HTTP/1.0 200 - Cyberduck/4.0.2%20%288601%29%20%28Windows%207/6.1%29%20%28x86%29 - - - - - - 0.0014 "200" is the desired response for GET command.
Please ignore my earlier comment, confusion happened at the same Junaid was using the cyberduck on Mac, Now, with 4.0.2 on windows, I am able to connect, list containers and objects with swift-plugin. Presently trying to upload file from cyberduck
Finally, tried the things on the latest version(4.2.1) of Cyberduck for Mac and Windows. Things are working, operations tested on both the OS:- 1. list the containers 2. list the objects 3. Rename of the smallobjects. 4. upload an object 5. download an object 6. delete an object/container. 7. creating sub-folders.
pre-release version is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.