[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs

[Tahoe-LAFS]

#3888: Handling Tor and i2p in NURLs
--------------------------+-----------------------------------
     Reporter:  itamarst  |      Owner:
         Type:  defect    |     Status:  new
     Priority:  normal    |  Milestone:  HTTP Storage Protocol
    Component:  unknown   |    Version:  n/a
   Resolution:            |   Keywords:
Launchpad Bug:            |
--------------------------+-----------------------------------

Comment (by itamarst):

 Re-reading:

 * Tor support in NURL scheme is not required. The client needs to detect
 .onion, yes, but that doesn't require a change in the URL scheme.
 * I2P does have extra options, but those are options the _client_ will
 want to decide, it's not related to the NURL the server puts out. So as
 long as no one makes a real conflicting .i2p TLD then you can do same
 thing as Tor.

 So real issue is maybe "are we doing right thing in HTTP client when given
 .onion and .i2p domains".

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3888#comment:11>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage