swift-server / swift-server/swift-http-server
Support certificate reloading without exposing NIO
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 44
- Forks
- 13
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 8
Description
Support for certificate reloading is currently available by initializing the TransportSecurity configuration with a CertificateReloader conformance.
CertificateReloader is defined in the NIOCertificateReloading product from swift-nio-extras, which transitively depends on NIO. Given that the goal of this package is to not expose NIO types, we should fix this.
See https://github.com/swift-server/swift-http-server/pull/34#discussion_r2607563166 for context and broader discussion.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Sources/HTTPServer/HTTPServerConfiguration.swift and its TransportSecurity configuration, then read the linked CertificateReloader API and the discussion in pull request 34. Determine an API for certificate reloading that does not expose NIO types; done means reloading remains supported without requiring a NIO-dependent public conformance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- backend, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100