Replies: 1 comment
-
You can use curl to perform the request manually, and then get the whole picture of what's wrong - you can send us the Debug log from Cyberduck either here or via support@cyberduck.io, when you want us to provide the curl command for you.
But, depending on your setup Apache might be unable to proxy the MOVE-verb to Artifactory. Footnotes |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When connecting with WebDAV HTTPS to our local Artifactory instance, Cyberduck connects properly and most functionality works well (upload, download, delete etc). However, when attempting to move or rename a file, Cyberduck throws a generic 500 Internal Server Error.
Artifactory does not provide any logs of the failed move or rename action. However, the local Apache config does show the request:
What can I do to determine the cause of this 500 error? I haven't been able to find any references of this issue with other users
Beta Was this translation helpful? Give feedback.
All reactions