Opened at 2022-07-25T14:16:54Z
Closed at 2023-06-26T13:02:03Z
#3910 closed task (fixed)
Storage HTTP server + client support for `.onion` NURLs
Reported by: | itamarst | Owned by: | GitHub <noreply@…> |
---|---|---|---|
Priority: | normal | Milestone: | HTTP Storage Protocol |
Component: | unknown | Version: | n/a |
Keywords: | Cc: | ||
Launchpad Bug: |
Description (last modified by itamarst)
- When a server is configured to listen on Tor, the announcement NURLs should include tor NURLs, instead of omitting them.
- The client should recognize Tor NURLs, and use Tor to talk to them.
Change History (5)
comment:1 Changed at 2022-07-25T14:21:14Z by itamarst
- Description modified (diff)
comment:2 Changed at 2023-05-12T13:21:08Z by itamarst
- Description modified (diff)
comment:3 Changed at 2023-05-15T19:52:13Z by itamarst
comment:4 Changed at 2023-06-06T13:09:59Z by itamarst
- Description modified (diff)
- Summary changed from Storage HTTP client that understands `.onion` NURLs to Storage HTTP server + client support for `.onion` NURLs
comment:5 Changed at 2023-06-26T13:02:03Z by GitHub <noreply@…>
- Owner set to GitHub <noreply@…>
- Resolution set to fixed
- Status changed from new to closed
In 0fb6c5a/trunk:
Note: See
TracTickets for help on using
tickets.
The reason integration test passes is because server doesn't send Tor NURLs, which means the client never received a NURL, which means the FURL is used.