Opened at 2022-06-10T13:49:42Z

Closed at 2022-10-04T14:32:17Z

#3902 closed task (fixed)

Storage nodes can start up with the HTTP storage protocol in addition to Foolscap

Reported by: itamarst Owned by: GitHub <noreply@…>
Priority: normal Milestone: HTTP Storage Protocol
Component: unknown Version: n/a
Keywords: Cc:
Launchpad Bug:

Description

  • Reuse the same certificate.
  • There should be a minimal integration or test_system test for this.

Change History (3)

comment:1 Changed at 2022-06-30T19:20:36Z by itamarst

Currently blocked by:

Can't be merged before:

Remaining work:

  • Make sure NURLs can be generated (one per Listener on the Tub?), ideally by switching test_istorageserver HTTP usage to the new protocol switch mechanism.
Version 0, edited at 2022-06-30T19:20:36Z by itamarst (next)

comment:2 Changed at 2022-09-15T14:10:41Z by itamarst

This also should make sure NURLs match the spec (or the spec matches the code). In particular, the spec assumes each NURL can have multiple host:port, whereas the code assumes multiple NURLs each with a single host:port.

comment:3 Changed at 2022-10-04T14:32:17Z by GitHub <noreply@…>

  • Owner set to GitHub <noreply@…>
  • Resolution set to fixed
  • Status changed from new to closed

In f56b434/trunk:

Merge pull request #1220 from tahoe-lafs/3902-listen-storage-http

Listen with storage HTTP protocol on same port as Foolscap

Fixes ticket:3902

Note: See TracTickets for help on using tickets.