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 OpenLink Virtuoso #10482
Comments
Any chance to post a transcript when executing |
@Yla -- As requested... There's no difference between this and the output for a folder which Cyberduck opens successfully, except the expected (i.e., timestamps, href, etag...)
|
Unable to generate a license
|
In the meantime I did some testing with the open source version 7.2. I was unable to replicate the issue with directory listing. The XML from the curl request you've posted looks fine but the content length is not the same as the original response above (1169 vs. 19167). It looks like you have emptied the folder. I would need a multistatus response that Cyberduck is unable to process.
|
Sorry for the hiccup. Looks like someone pushed an unrelated patch, and didn't check all its dependents. To get Enterprise Edition (v7.2 or 8.1), please revisit the download page, and use the "login" link at upper right. You can use any of your existing social logins through the buttons in the dialog that comes up, or click Register to create a new user account on the OpenLink download & shop system. Then pick the version you want to test, and your preferred OS, and the rest should be clear. (Note that a license for v8 will permit use of either v8 or v7.) It appears to me that some request header is not being shown in the Cyberduck log pane, as I consistently get the 19167 size when trying to open that directory with Cyberduck, and the 1169 size running I am relaying the issue with |
The equivalent
Can you please execute this one? |
|
Thanks! This is also a server side issue responding with an invalid XML. There is something wrong with the handling of custom properties for a file in this folder which are set by Cyberduck after an upload:
My test instance (and probably most of your folders) correctly returns the custom properties as follows:
It would be great if you could forward this issue to the dev team too. |
''Listing directory Editorial_Processing failed.
Not a valid DAV response (207 Multi-Status). Please contact your web hosting service provider for assistance.''
This occurs when trying to drill down in some directories, and when trying to copy into some initial mountpoints.
Please see RFC 4918: HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
The target WebDAV server is OpenLink Virtuoso Enterprise Edition running on Linux. If helpful, you can put your own test instance on Linux, Windows, or macOS. A two-week trial license will be provided with installer download; I can extend this as/if needed. (The only think to change is the license file; all software, configuration, etc., will remain in place.)
Open Source Edition (VOS) may also be suitable for a test deployment. Prebuilt binaries are available, as is full source.
The text was updated successfully, but these errors were encountered: