1 個回答
- 最新
- 最多得票
- 最多評論
1
Are you using Proxy Resource?
Seems like your issue is that API gateway is not forwarding the URL path to NLB, so your backend is always returning the content of https://pingaccess.dev.obiebank.obly.io/
(which most likely is an HTML page)
If you don't want to specify all possible URL path in the API gateway, using proxy resource is the way to capture all URL suffix and forward to the backend.
https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-set-up-simple-proxy.html
已回答 2 年前
相關內容
- 已提問 6 個月前
- 已提問 6 個月前
- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
Hi RichardFan , Thanks for responding. YES, we are using Proxy resource and we have mention greedy Proxy path
{proxy+}
to handle all context paths.