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.

Sign up for GitHub

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

Jump to bottom

chore: publish the doc about zero byte files #164

Merged
merged 1 commit into from
May 24, 2024
Merged

chore: publish the doc about zero byte files #164

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions source/_includes/sidebar.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,7 @@
<li><a href="{{ site.url }}/dav/sync">WebDAV sync</a></li>
<li><a href="{{ site.url }}/dav/writing-plugins">Writing Plugins</a></li>
<li><a href="{{ site.url }}/dav/xmlelements">XML Elements</a></li>
<li><a href="{{ site.url }}/dav/0bytes">Zero byte files</a></li>
</ul>
</li>
</ul>
Expand Down
12 changes: 6 additions & 6 deletions source/dav/0bytes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
title: 0 byte files
title: Zero byte files
layout: default
---

There are a number problems that can cause empty files to appear on the server.
There are a number of problems that can cause empty files to appear on the server.
Because there are a number of different scenarios that can result in 0 byte
files, it's good to try to figure out which specific issue is the one you're
dealing with.
Expand All @@ -16,7 +16,7 @@ There are a number of clients, in particular [OS X's Finder](/dav/clients/finder
and [Transmit](/dav/clients/transmit) that use the so-called 'chunked transfer'
encoding to create new files.

There are many webservers that do not support this. We recommend to use Apache
There are many webservers that do not support this. We recommend using Apache
with mod_php (not fastcgi) or **a recent version** of nginx. Avoid Lighttpd.

When servers don't properly support chunked transfer encoding, the end result
Expand Down Expand Up @@ -48,7 +48,7 @@ WebDAV clients, receiving an empty 0-byte file first is expected.
Locking
-------

Furthermore, there are clients that support `LOCK`. Clients may `LOCK` a url
Furthermore, there are clients that support `LOCK`. Clients may `LOCK` a URL
before creating a new file. The idea is that while the file is locked, some
other client cannot start creating a file with the same name.

Expand All @@ -57,13 +57,13 @@ initial webdav standard ([rfc2518][1]) differs from the updated standard
([rfc4918][2]). SabreDAV follows the recommendation from the latest
specification.

That is: If a client makes a `LOCK` request on a url that _does not yet_
That is: If a client makes a `LOCK` request on a URL that _does not yet_
exist, SabreDAV itself will create an empty file at that location.

So this is another situation where an empty file may be created before the
_actual_ file comes in.

Another reason might be, that the lock-file could not be created due to a nonexistent folder or insufficient permissions.
Another reason might be that the lock-file could not be created due to a nonexistent folder or insufficient permissions.
Check your logfiles for errors.

What if there is no follow-up PUT?
Expand Down
Loading