1 Answer
- Newest
- Most votes
- Most comments
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
answered 2 years ago
Relevant content
- asked 5 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Hi RichardFan , Thanks for responding. YES, we are using Proxy resource and we have mention greedy Proxy path
{proxy+}
to handle all context paths.