Repository navigation
[Migrated from ohttp-relay] - Make GATEWAY_ORIGIN optional or remove entirely #1240
Description
Which crate is this feature request for?
ohttp-relay
Please describe the feature you'd like to see added.
With gateway opt-in it seems unnecessary to require GATEWAY_ORIGIN. Having a hardcoded default server also resulted in a confusing issue where the ohttp relay would forward requests to the wrong server if the directory path was missing from the request URL (see #1166).
Is your feature related to a problem, if so please describe it.
No response
Describe the solution you'd like
No response
Describe any alternatives you've considered
No response
Please leave any additional context
Originally posted in ohttp-relay payjoin/ohttp-relay#73
Activity
[-][ Migrated from ohttp-relay ] - Make GATEWAY_ORIGIN optional or remove entirely[/-][+][Migrated from ohttp-relay] - Make GATEWAY_ORIGIN optional or remove entirely[/+]nothingmuch commentedon Dec 18, 2025
I believe this can be closed, since that environment variable is mainly for backwards compatibility, and #1232 obviates the need for that
As for the behavior of having a default gateway at all, we should ask relay operators if they see any requests using the old URI and we can probably remove that too if 0.24 is widespread
spacebear21 commentedon Dec 18, 2025
Both cake wallet and bull bitcoin mobile are on 0.23 still, so we do need to keep it for the foreseeable future.
benalleng commentedon Dec 18, 2025
Ok lets leave it open for now then
spacebear21 commentedon Mar 13, 2026
The default gateway is now simply hardcoded to "payjo.in" in payjoin-mailroom to ensure backwards compatibility until cake and BBM upgrade.