Re: Encrypted Storage on WebDAV
Re: Encrypted Storage on WebDAV
- Subject: Re: Encrypted Storage on WebDAV
- From: email@hidden
- Date: Wed, 22 Nov 2006 14:17:27 +0100 (MET)
Hi Jim,
The problem is that the PUT method does not support ranges. <http://
lists.w3.org/Archives/Public/ietf-http-wg/1997OctDec/0011.html>
gives the reason why PUT-RANGE wasn't left in the HTTP 1.1
specification and <http://www.w3.org/Protocols/HTTP/Issues/
BeforeLastCall.html#PUT-RANGE> is where PUT-RANGE was officially
removed from Rev-02 of the HTTP 1.1 spec.
I agree with the reason ranged PUT support was removed from the
HTTP 1.1 spec -- there are servers that ignore the Range header on
a PUT, and so you'd end up with data loss on those servers.
Ah, I never thought of that kind of problem with partial PUT. This is
indeed a valid reason not to support it.
In any event, fixing the WebDAV file systems to handle ranges up
and down (once a PATCH method is available) will require a major
rewrite (I worked on WebDAV FS for several years, so I know).
I presume WebDAV currently does clever caching to hide the high
latency backend from applications requiring something like an mmap
interface. I can image that one does not want to rewrite such code...
I suggest you store your secure data on another type of network
volume -- AFP, NFS, or SMB.
I think I will go that route. Thanks for your insights.
Michael
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden