-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Bug with external Alfresco WebDAV (RFC-compliant) server #16471
Comments
Mind to add the raw response from alfresco? Check #15363 (Curl Logs) |
There is a gap in the code 🤔 server/lib/private/Files/Storage/DAV.php Lines 250 to 284 in 631ae17
We have no cached response and call propfind. The response is faulty, a expection is thrown, catched and passed to convertException but there is no code to handle this kind of failure. Code reaches the last return statment without initializing $response. server/lib/private/Files/Storage/DAV.php Line 834 in 631ae17
Could you change the logging level to |
Hi @kesselb please find Debug log here attached. |
I can also provide a test server if needed.
|
I've also tried the patch at #15363 (comment) and no help in this specific case. |
Thanks 👍 |
This comment has been minimized.
This comment has been minimized.
OK. The above response is fine. I extracte the "parse response" code into a single script: https://github.com/kesselb/nextcloud-dav I think we need a different response from alfresco. I assume the external share is called Alfresco and resolves to http://ip_here/alfresco/webdav/Webdav. Mind to propfind http://ip_here/alfresco/webdav/Webdav/Nextcloud.mp4 and share the response? It might be easier to add some debug code to nextcloud but don't use this on production and remove it after you reproduced the problem / triggered the exception.
|
And the |
Hmm. The responses are fine. I think we need a different patch here:
Please delete |
|
Thanks 👍
Correct response (with 1+ elements in props) Faulty response (with no elements in props) |
Just one more hint; if a file is MOVED into the "Alfresco" folder (WebDAV root) and then I go into that folder, it is empty (but if i just upload or COPY a new file into it, i can see that file). |
For now, we've mounted our Alfresco trough |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
in V17.0 this still fails:
|
There is a note in their website that states:
Can this be related (and fixed)? |
With newer Nextcloud versions, a new exception is thrown, maybe it helps solving this:
Followed by:
|
Is this Issue still valid in NC21.0.2? If not, please close this issue. Thanks! :) |
Yes, this still valid with 21.0.2 and the error message is exactly the same. |
Fix for sabre/dav to parse prop properly: sabre-io/dav#1355 |
PR to update sabre/dav: nextcloud/3rdparty#954 |
nextcloud/3rdparty#936 was merged a while ago. Should work now for Nextcloud 24 ;) |
@szaimen It does not work for Nextcloud 24? 😞 |
Reopened this wrongly. Sorry! |
This is a weird bug.
I've configured a test setup including both Alfresco - they claim a RFC-compliant DAV implementation: https://docs.alfresco.com/6.0/concepts/troubleshoot-webdav.html - and Nextcloud on the same server using docker (official NC docker image, using SQLite) on Ubuntu 18.04. Connection between both is well established (there is no encryption/TLS involved on the connection).
On the initial WebDAV setup (accessing Alfresco files trough WebDAV on Nextcloud) I've uploaded two files and checked if they were well uploaded on Alfresco. No problem.
But, if i upload any new file or create any new folder trough Nextcloud, i can only see that new file/folder, and not previously uploaded files or existent folders. Files or folders are well visible on Alfresco, previous and new ones. And it reproduces any time I upload any new file OR create any new folder trough Nextcloud interface on the DAV folder.
Only this new content is visible on Nextcloud interface (or mobile apps), not previous content on the DAV (Alfresco) server.
But if i try to re-upload an existent file, NC claims it already exists and if it should be rewrite, even if the file is not visible.
The only lines write on the log files are these:
If any further info is needed, I'll be glad to provide it.
The text was updated successfully, but these errors were encountered: