-
Notifications
You must be signed in to change notification settings - Fork 27
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: cache is not updated if the file size has not changed #31
Comments
My implementation: I can’t help but say that the PATCH option proposed by SabreDav is redundant. It is not clear why it was necessary to require the range to be specified if Content-Length was available. How and what should the server do if the sizes do not match. The ability to write at an offset from the end of the file seems useless. After all, the only real application of this method is an implementation similar to webdavfs. And for this, a simple indication of the offset from the beginning of the file is enough. That's all. The append mode is actually not needed either. |
I'm writing
PATCH
support for a standard webdav server in go. While I was testing differentbytes=A-B
, I noticed that if the file size did not change after the operation, then the old version of the file would be displayed on the local file system. You can restart the web server, rewrite the file 100 times on the server or client (but without changing the size), wait a hour, but the client will still have the old version of the file without changes.I also tested dufs to make sure that the problem is not in my implementation. There's a problem there too.
Perhaps I still made a mistake somewhere. But I suggest you check with your webserver too.
The text was updated successfully, but these errors were encountered: