Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Stephen <hnehpets@yahoo.com>
Content-Type: multipart/alternative;
	boundary=Apple-Mail-5B9FC9A3-FD56-4AA3-81D2-A6BEC0756876
Message-Id: <E09B418D-1D37-4CD0-9CF5-D9A751F35B4E@yahoo.com>
Date: Tue, 17 Dec 2013 10:29:27 -0500
To: "users@httpd.apache.org" <users@httpd.apache.org>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: [users@httpd] mod_dav: resume transfers not working

--Apple-Mail-5B9FC9A3-FD56-4AA3-81D2-A6BEC0756876
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

All,

Forgive me if I am not asking this question in the right way. If I should po=
st it somewhere else, please let me know.

I have been racking my brain as to why some uploads via webdav are failing t=
o resume.  I have some users that are uploading 10GB plus files and are tryi=
ng to resume them when they have a connection timeout with no success. If th=
ere is no timeout on the connection, it works.  We see the following:

1) client starts the upload
2) client timeout (we pull a network cable to simulate)
3) partial file on the server
3) client tries to resume with an active network connection
4) client does a PROPFIND for the file on the server and gets a status 404
5) server deletes the file
6) client resume fails and starts over from scratch.


We pretty much have the standard config per documentation on the  server...h=
ttp://httpd.apache.org/docs/2.2/mod/mod_dav.html

I have tried multiple clients that support resume (cyberduck and crossftp). =
 Both state "Some servers may not support resumable transfers and the file w=
ill be reloaded instead."  What is it specifically that has to be implemente=
d on a server to support resumable transfers?

Cyberduck: 4.4.4
CrossFTP 1.91.2
Centos 5.7
Apache 2.2.15

Thanks,
stephen=

--Apple-Mail-5B9FC9A3-FD56-4AA3-81D2-A6BEC0756876
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><div><div><div><div><div><div><div><di=
v><div><span style=3D"-webkit-text-size-adjust: auto; background-color: rgba=
(255, 255, 255, 0);">All,<br><br></span></div><span style=3D"-webkit-text-si=
ze-adjust: auto; background-color: rgba(255, 255, 255, 0);">Forgive me if I a=
m not asking this question in the right way. If I should post it somewhere e=
lse, please let me know.<br><br></span></div><span style=3D"-webkit-text-siz=
e-adjust: auto; background-color: rgba(255, 255, 255, 0);">I have been racki=
ng my brain as to why some uploads via webdav are failing to resume.&nbsp; I=
 have some users that are uploading 10GB plus files and are trying to resume=
 them when they have a connection timeout with no success. If there is no ti=
meout on the connection, it works. &nbsp;We see the following:<br><br></span=
></div><span style=3D"-webkit-text-size-adjust: auto; background-color: rgba=
(255, 255, 255, 0);">1) client starts the upload<br></span></div><span style=
=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0)=
;">2) client timeout (we pull a network cable to simulate)<br></span></div><=
div><span style=3D"-webkit-text-size-adjust: auto; background-color: rgba(25=
5, 255, 255, 0);">3) partial file on the server<br></span></div><span style=3D=
"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">=
3) client tries to resume with an active network connection<br></span></div>=
<span style=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 2=
55, 255, 0);">4) client does a PROPFIND for the file on the server and gets a=
 status 404<br></span></div><span style=3D"-webkit-text-size-adjust: auto; b=
ackground-color: rgba(255, 255, 255, 0);">5) server deletes the file<br></sp=
an></div><span style=3D"-webkit-text-size-adjust: auto; background-color: rg=
ba(255, 255, 255, 0);">6) client resume fails and starts over from scratch.<=
br><br><br></span></div><span style=3D"-webkit-text-size-adjust: auto; backg=
round-color: rgba(255, 255, 255, 0);">We pretty much have the standard confi=
g per documentation on the&nbsp; server...<a href=3D"http://httpd.apache.org=
/docs/2.2/mod/mod_dav.html">http://httpd.apache.org/docs/2.2/mod/mod_dav.htm=
l</a><br><br></span></div><div><span style=3D"-webkit-text-size-adjust: auto=
; background-color: rgba(255, 255, 255, 0);">I have tried multiple clients t=
hat support resume (cyberduck and crossftp).&nbsp; Both state "Some servers m=
ay not support resumable transfers and the file will be reloaded instead."&n=
bsp; What is it specifically that has to be implemented on a server to suppo=
rt resumable transfers?</span></div><div><span style=3D"-webkit-text-size-ad=
just: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div=
><span style=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 2=
55, 255, 0);">Cyberduck: 4.4.4</span></div><div><span style=3D"-webkit-text-=
size-adjust: auto; background-color: rgba(255, 255, 255, 0);">CrossFTP 1.91.=
2</span></div><div><span style=3D"-webkit-text-size-adjust: auto; background=
-color: rgba(255, 255, 255, 0);">Centos 5.7</span></div><div><span style=3D"=
-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">A=
pache 2.2.15<br><br></span></div><div><span style=3D"-webkit-text-size-adjus=
t: auto; background-color: rgba(255, 255, 255, 0);">Thanks,<br>stephen</span=
></div></body></html>=

--Apple-Mail-5B9FC9A3-FD56-4AA3-81D2-A6BEC0756876--