* download/upload localdir=/localfile= has been removed. This sort of ambient
authority was unsafe to expose over the web (CSRF), and at some point
soon we'll have 'cp -r' in the CLI to replace it.
* GET save=filename -> GET filename=filename&save=true
* GET t=download removed
* side-effect causing operations now use POST where appropriate, not PUT
* to create multiple directories, either use
* POST /uri/DIRCAP/parent?t=mkdir&name=child (more form/browser oriented)
* POST /uri/DIRCAP/parent/child?t=mkdir (more machine oriented)
The t=mkdir-p form is still accepted, but not preferred (since it leaks
the child name queryarg into the logs)
* use PUT /uri/MUTABLEFILECAP or PUT /uri/DIRCAP/child (on a mutable file) to
replace its contents, or POST /same?t=upload from forms
* response bodies and codes are better specified than before
a typo in the 'flags2mode' code would wind up passing the O_APPEND
flag into the os open() call, which would cause the file to be opened
in 'strict append' mode, i.e. all writes extend the file, regardless of
calls to seek.
this causes a problem for tahoefuse in that the seek() calls made to
filehandles open through fuse would be ignored when write()s occurred.
this was evidenced by corruption seen when using rsync. it turns out
that rsync actually makes overlapping writes in some cases, i.e. even
when writing a new fresh file out, it still doesn't write a simple
contiguous span of data, but will make writes overlapping data already
written. this is probably related to the way it manages data blocks
internally for rolling checksums etc. at any rate, this bug would
thus cause rsync in those cases to write a chunk of duplicate data
into the file - leading to tahoe securely and reliably storing the
wrong data.
fixing this, so that non-append file opens do not pass O_APPEND seems
to eliminate this problem.
previously tahoefuse returned the fs stat for the filesystem the fuse plugin
was running upon (e.g. '/'). this works ok until you need to copy more to
tahoe than the local machine has free disk space, at which point Finder will
refuse to copy 'too much' data.
this changes it so that tahoe always reports 2TiB used of an 8TiB filesystem
this is entirely bogus, but allows copies of up to 2TiB to be initiated.
