-
Notifications
You must be signed in to change notification settings - Fork 159
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
Problem writing new files when mounted as share in OS X (10.7.4) #47
Comments
jsDAV has changed A LOT in two years. Current release is v0.3.0. Closing this issue, because it cannot be reproduced. If you find this decision to be in error, please reopen the issue. |
I can't reproduce it any more either. Could either be a change in webdav or (less likely) OS X, since I'm on 10.8.2 now. |
you tried with the new jsDAV or the same one? |
I checked it out of your repo just before I posted the comment and followed the same steps as in the original report. I haven't been following jsDAV lately so I don't know how much it's changed in the 9 months since I opened the original report. |
Ah! well, a lot has changed, but thanks for confirming this :) |
Steps to reproduce problem:
Run
test/test_server.js
Mount folder using finder.
cd /Volumes/localhost
followed byecho sometext > newfile
.At this point, on my system (OS X 10.7.4), both Finder and Terminal then hang, and I have to kill the node process using Activity Monitor. It seems that the file itself is created and the data is written to it, but there is some problem caused by the PROPFIND or UNLOCK requests which the OS X webdav implementation makes following creation of the new file. I haven't figured it out exactly yet.
If
newfile
is replaced by the name of an existing file, the problem does not seem to arise.The text was updated successfully, but these errors were encountered: