[tahoe-dev] [tahoe-lafs] #958: LAFS 301 Moved Permanently

[tahoe-lafs]

#958: LAFS 301 Moved Permanently
------------------------------+---------------------------------------------
     Reporter:  zooko         |       Owner:                                                                                                                            
         Type:  enhancement   |      Status:  new                                                                                                                       
     Priority:  major         |   Milestone:  soon                                                                                                                      
    Component:  code-mutable  |     Version:  1.6.0                                                                                                                     
   Resolution:                |    Keywords:  forward-compatibility backward-compatibility integrity newcaps newurls http sftp ftpd smb availability security revocation
Launchpad Bug:                |  
------------------------------+---------------------------------------------

Comment (by zooko):

 Hm, would it be okay to allow people to set an HTTP 301 to a different cap
 of a different ''type'', such as a read-write cap instead of a read-only
 cap or a read-only cap instead of a read-write cap?

 Our tradition of transitive attenuation of authority suggests that we
 should forbid this, which means that a client which is ''following'' an
 HTTP 301 redirect should remember whatever the attenuation of the original
 cap was (i.e. if it was read-only or ''???'' if it was a verify-only cap)
 and refuse to use the new cap with authority outside of that.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/958#comment:15>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage