[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
 Keywords:            |  Launchpad Bug:
----------------------+---------------------------------------
 NURLs, the new furl replacement that is HTTP based, does not currently
 support Tor or i2p syntactically. It just has a hostname field... The
 `hyperlink` library also has issues with parsing it if is forced in to the
 hostname, which may be legitimate "this is not a valid URI/URL" complaint.

 One alternative is to switch to combo protocol URLs, e.g.:

 {{{
 pb://1WUX44xKjKdpGLohmFcBNuIRN-8rlv1Iij_7rQ@127.1:34399/jhjbc3bjbhk#v=1
 pb+tor+https://1WUX44xKjKdpGLohmFcBNuIRN-
 8rlv1Iij_7rQ at 127.1:34399/jhjbc3bjbhk#v=1
 pb+i2p://1WUX44xKjKdpGLohmFcBNuIRN-8rlv1Iij_7rQ@sdsdfsdfds/jhjbc3bjbhk#v=1
 }}}

 Changing the NURL to this could be backwards compatible if `pb://` is
 synonym for normal HTTPS, as above.

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