Skip to content

Conversation

@arminsabouri
Copy link

OHTTP 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.


This work was first started by @alexlwn123
Tested against a blockstream's electrs and running an OHTTP relay and OHTTP Gateway locally. Automated tests are still TODO.

Seeking concept Ack/Nack

Co-authored-by Alex Lewin <[email protected]>

[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.
@luisschwab luisschwab self-requested a review December 9, 2025 01:14
@luisschwab
Copy link
Member

Concept ACK, this is a cool ideia. We are, however, in the process of completely dropping reqwest/minreq in favor of bitreq. Can you change the PR to use that?

@arminsabouri
Copy link
Author

Concept ACK, this is a cool ideia. We are, however, in the process of completely dropping reqwest/minreq in favor of bitreq. Can you change the PR to use that?

Sure. Looks like the bitreq migration is a WIP #137. I may wait till thats in good shape before rebasing my commits on top of that.

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.

2 participants