[tahoe-dev] [tahoe-lafs] #626: The wapi ought to cope with slashes

[tahoe-lafs]

#626: The wapi ought to cope with slashes
--------------------------------------------+-------------------------------
 Reporter:  kpreid                          |           Owner:  warner   
     Type:  defect                          |          Status:  new      
 Priority:  minor                           |       Milestone:  undecided
Component:  code-frontend-web               |         Version:  1.3.0    
 Keywords:  /, slashes, URL encoding, wapi  |   Launchpad_bug:           
--------------------------------------------+-------------------------------

Comment(by davidsarah):

 This bug seems inconsistent with the design decision made in #75.

 I would argue against allowing slashes in Tahoe filenames, even at a low
 level. Almost all filesystems disallow slashes (and NULs), so we don't
 need them to interoperate with other filesystems. Having different rules
 about which filenames are allowed at different levels can only cause
 problems.

 Note that the POSIX definition of a filename, at
 http://www.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_169
 , is:
 > A name consisting of 1 to {NAME_MAX} bytes used to name a file. The
 characters composing the name may be selected from the set of all
 character values excluding the slash character and the null byte. The
 filenames dot and dot-dot have special meaning. A filename is sometimes
 referred to as a "pathname component".

 I suggest resolving this as invalid. (We do need to think more carefully
 about what filenames are allowed, but that is covered by other bugs, such
 as #731.)

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/626#comment:2>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid