Opened at 2022-04-06T15:40:28Z
Last modified at 2023-07-05T14:18:30Z
#3888 closed defect
Handling Tor and i2p in NURLs — at Version 1
Reported by: | itamarst | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | HTTP Storage Protocol |
Component: | unknown | Version: | n/a |
Keywords: | Cc: | ||
Launchpad Bug: |
Description (last modified by itamarst)
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://1WUX44xKjKdpGLohmFcBNuIRN-8rlv1Iij_7rQ@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.
Change History (1)
comment:1 Changed at 2022-04-06T15:40:54Z by itamarst
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.