[tahoe-dev] Ideas: Putting the read-cap after the URL fragment; HTML+JS payloads

Tue Jul 5 21:06:10 PDT 2011

On 05/07/11 00:40, James A. Donald wrote:
> On 2011-07-02 12:52 AM, Manuel Simoni wrote:
>> Hi Tahoe folks!
>>
>> I've been thinking about two issues related to Tahoe+Web:
>>
>> By putting the read-cap after the URL fragment, e.g.
>>
>>     http://example.com/path/to/file#cap
>>
>> one can guarantee that the cap is never sent over the network
> 
> Everything is apt to get sent over the network by various add ons.
> 
> The method least likely to be leaked is post, rather than get.

Right, which is what ticket #127 settled on
(http://tahoe-lafs.org/trac/tahoe-lafs/ticket/127#comment:21).

-- 
David-Sarah Hopwood ⚥ http://davidsarah.livejournal.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 294 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110706/fcf9aa1a/attachment.pgp>