Skip to content

WIP - OHTTP integration take two - #254

Draft
arminsabouri wants to merge 1 commit into
bitcoindevkit:masterfrom
arminsabouri:ohttp-client-lib
Draft

arminsabouri wants to merge 1 commit into
bitcoindevkit:masterfrom
arminsabouri:ohttp-client-lib

Conversation

@arminsabouri

Copy link
Copy Markdown

Alternative implementation that spun off #145. This implementation uses the ohttp-client crate which reduces ohttp boilerplate in both the actual implementation and tests (the crate ships with a test harness) .

[OHTTP](https://datatracker.ietf.org/doc/rfc9458/) lets a client
send encrypted requests through a relay so the server can’t see
who sent them and the relay can’t see what they contain.
The following commit adds optional configurations to enable
clients to proxy their requests through an OHTTP relay and gateway.

OHTTP functionality is feature flagged off behind `async-ohttp`. If a
client provided OHTTP config it will attempt to use the relay
instead of the target resource directly.

style(docs): rewrap `async-ohttp` feature list entry

Nightly rustfmt wraps doc comments; stable ignores `wrap_comments`, so
the local format check passed while CI failed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant