Use proxy agents for CLNRest over Tor #1136
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Close #1107 Supersedes #1133
This now uses copied proxy agents from
hpagent
.CLNRest should now work with HTTPS over clearnet (as already did) and with HTTP/HTTPS over Tor.
Screenshots
Additional Context
Checklist
Are your changes backwards compatible? Please answer below:
yes
Did you QA this? Could we deploy this straight to production? Please answer below:
I tested that the correct agents are called depending on
/\.onion(:[0-9]+)?$/.test(socket)
andcert
. I didn't e2e test this to save time and because I am confident enough that this works. So I would say let's try this out in production.For frontend changes: Tested on mobile? Please answer below:
Did you introduce any new environment variables? If so, call them out explicitly here: