-
Notifications
You must be signed in to change notification settings - Fork 667
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
Uploaded files disappear from the server #39
Comments
FYI: we use litmus within ci since our meeting in Berlin. Litmus is a webdav compliance test suite. @jakobsack you think this is related? Thx |
@MTRichards: is this still reproducable for you? |
Closing due to lack of comments. |
Some files that are uploaded through WebDav are missing from the ownCloud server. The access logs shows that the files have been uploaded successfully, but when I check the filesystem, there's nothing there.
Here's an example:
85.19.27.238 - rmk [01/Nov/2012:12:57:26 +0100] "PROPFIND /remote.php/webdav/ HTTP/1.1" 207 6186
85.19.27.238 - rmk [01/Nov/2012:12:57:26 +0100] "PROPFIND /remote.php/webdav/Privat HTTP/1.1" 207 12599
85.19.27.238 - rmk [01/Nov/2012:12:57:26 +0100] "PUT /remote.php/webdav/Privat/Faktureringslogg%20fom%20010411%20-%201.xlsx HTTP/1.1" 201 -
85.19.27.238 - rmk [01/Nov/2012:12:57:26 +0100] "PROPFIND /remote.php/webdav/Privat/Faktureringslogg%20fom%20010411%20-%201.xlsx HTTP/1.1" 404 321
85.19.27.238 - rmk [01/Nov/2012:12:57:26 +0100] "PROPFIND /remote.php/webdav/Privat HTTP/1.1" 207 12599
85.19.27.238 - rmk [01/Nov/2012:12:57:27 +0100] "PROPPATCH /remote.php/webdav/Privat/Faktureringslogg%20fom%20010411%20-%201.xlsx HTTP/1.1" 404 321
85.19.27.238 - rmk [01/Nov/2012:12:57:27 +0100] "PROPFIND /remote.php/webdav/Privat HTTP/1.1" 207 12599
The PUT request is responding with "201", indicating that the file has been created successfully. And then, in the next request, the server responds with code 404, which tells us that the file isn't there. How can this happen?
ownCloud 4.5.1a, with client 1.1.1.
The text was updated successfully, but these errors were encountered: