Skip to content
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

WebDav Locking (WebDrive) not working #2166

Closed
bboule opened this issue Mar 7, 2013 · 9 comments
Closed

WebDav Locking (WebDrive) not working #2166

bboule opened this issue Mar 7, 2013 · 9 comments

Comments

@bboule
Copy link

bboule commented Mar 7, 2013

Using Ubuntu 12.04 with MySQL and Apache accessing files via webdav client (WebDrive) file locking is not working properly. ownCloud doesn't report the correct lock tokens during PROP requests.

@blizzz
Copy link
Contributor

blizzz commented Mar 7, 2013

Could you please give more details, best using this template? Thanks! https://raw.github.com/owncloud/core/master/issue_template.md

@karlitschek
Copy link
Contributor

@bartv2 Do you know how and if we support the locking here at all?

@bartv2
Copy link
Contributor

bartv2 commented Mar 8, 2013

yes we implement locking, most of the work is done in SabreDav. We check our implementation with litmus.

@bboule can you try to run the litmus webdav test suite on your server to check the configuration?

@KimSRT
Copy link

KimSRT commented Mar 11, 2013

Bboule,

Someone would be happy to assist you if you visit our online helpdesk at www.srthelpdesk.com (I work for the publisher of this application). Once you are there, simply click "Submit a Ticket" and please describe your problem in detail. If you could also include a debug log, that would be appreciated. Someone will respond to you as soon as possible.

Thanks!

@bboule
Copy link
Author

bboule commented Mar 13, 2013

Hey guys sorry I got pulled away from this, @bartv2 let me try running the litmus test suite and report back

@karlitschek
Copy link
Contributor

@bboule Any news on that?

@bboule
Copy link
Author

bboule commented Apr 12, 2013

Guys, I am going to deal with this today, I will keep you posted, the more I dig at this the more I think this is a client specific issue, but my plan is to run the litmus test assuming it passes for the lock, I will go back to the WebDav client developer and present this to them and ask for assistance. I will close this for now and re-open if needed. Apologies for the delay on this one!! I will also test this against OC 5!!

@bboule bboule closed this as completed Apr 12, 2013
@neoscopio
Copy link

Hi,

I'm also having problems with locking:

In linux, I open kate, open a txt file via web dav in computer 1 and computer 2, make changes,
Save computer 1, save computer 2, computer 2 complains, but it saves anyway then loosing changes made by computer 1.

I've just run the litmus tests.

-> running `basic':

  1. init.................. pass
  2. begin................. pass
  3. options............... pass
  4. put_get............... pass
  5. put_get_utf8_segment.. pass
  6. put_no_parent......... pass
  7. mkcol_over_plain...... pass
  8. delete................ pass
  9. delete_null........... pass
  10. delete_fragment....... pass
    1. mkcol................. pass
    2. mkcol_again........... pass
    3. delete_coll........... pass
    4. mkcol_no_parent....... pass
    5. mkcol_with_body....... pass
    6. finish................ pass
      <- summary for basic': of 16 tests run: 16 passed, 0 failed. 100.0% -> runningcopymove':
  11. init.................. pass
  12. begin................. pass
  13. copy_init............. pass
  14. copy_simple........... pass
  15. copy_overwrite........ pass
  16. copy_nodestcoll....... pass
  17. copy_cleanup.......... pass
  18. copy_coll............. pass
  19. copy_shallow.......... pass
  20. move.................. pass
    1. move_coll............. pass
    2. move_cleanup.......... pass
    3. finish................ pass
      <- summary for copymove': of 13 tests run: 13 passed, 0 failed. 100.0% -> runningprops':
  21. init.................. pass
  22. begin................. pass
  23. propfind_invalid...... pass
  24. propfind_invalid2..... pass
  25. propfind_d0........... pass
  26. propinit.............. pass
  27. propset............... pass
  28. propget............... pass
  29. propextended.......... pass
  30. propmove.............. pass
    1. propget............... pass
    2. propdeletes........... pass
    3. propget............... pass
    4. propreplace........... pass
    5. propget............... pass
    6. propnullns............ pass
    7. propget............... pass
    8. prophighunicode....... pass
    9. propget............... FAIL (Property {http://example.com/neon/litmus/}high-unicode had value , expected ?)
    10. propremoveset......... pass
    11. propget............... pass
    12. propsetremove......... pass
    13. propget............... pass
    14. propvalnspace......... pass
    15. propwformed........... pass
    16. propinit.............. pass
    17. propmanyns............ pass
    18. propget............... pass
    19. propcleanup........... pass
    20. finish................ pass
      <- summary for `props': of 30 tests run: 29 passed, 1 failed. 96.7%
      See debug.log for network/debug traces.

note: "?" on the error is an recognizable character

@neoscopio
Copy link

Version ownCloud 5.0.4 (sorry)

@lock lock bot locked as resolved and limited conversation to collaborators Aug 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants