You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a new environment variable to set a prefix in the routes. I would like to prefix the routes with /bitgo for example so /api/v2/pingexpress would become /bitgo/api/v2/pingexpress.
Motivation
The need arises because I am sharing AWS Load Balancers between different services and the prefix is the one routing requests to the corresponding service. So the service would need to accept the prefix before its routes.
Context
The text was updated successfully, but these errors were encountered:
Hi @mmcshinsky-bitgo thanks for your quick reply. I had already tried with BITGO_CUSTOM_ROOT_URI=https://0.0.0.0:3080/bitgo
but the result was:
customRootUri or customBitcoinNetwork is set, but env is 'test'. Setting env to 'custom'.
Environment: custom
BitGo-Express running
Custom root URI: https://0.0.0.0:3080/bitgo
Base URI: https://0.0.0.0:3080
error 404: bitgo-express can only proxy BitGo API requests
1.0.78.237 - local_express [14/Sep/2022:19:18:37 +0000] "GET /bitgo/api/v2/pingexpress HTTP/1.1" 404 176 "-" "PostmanRuntime/7.29.2"
failed to fetch initial client constants from BitGo
As you can see in GET /bitgo/api/v2/pingexpress/bitgo/ prefix still appears. I don't know if I'm configuring something wrong.
Feature Description
Add a new environment variable to set a prefix in the routes. I would like to prefix the routes with
/bitgo
for example so/api/v2/pingexpress
would become/bitgo/api/v2/pingexpress
.Motivation
The need arises because I am sharing AWS Load Balancers between different services and the prefix is the one routing requests to the corresponding service. So the service would need to accept the prefix before its routes.
Context
The text was updated successfully, but these errors were encountered: