Score:0

Cannot seem to connect to Amazon API Gateway with PORT on Request URI

uz flag

I am working on a mobile application that is connecting to a legacy web application using a request such as this:

https://example.com:8000/api/user/login

We are migrating certain functionality from the API server and we thought it best to use an API Gateway to do this. We were able to create and deploy an API Gateway with the custom domain map (by mapping the deploy stage to the domain and creating an ALIAS record to the API Gateway in Route53).

The API Gateway consists of an API resource with 60+ resources nested under. Each method has a proxy HTTP integration type to a Classic Load Balancer which routes the requests to the legacy web application.

There is a strange problem. The API only seems to work without the port 8000 as part of the request URI. Since all requests from the mobile app has the port 8000, I get timeouts. However, when I remove the port, all requests pass through successfully. I enabled logs and realized that the requests don't even reach the Gateway when the port is present.

Unfortunately we cannot, at the moment, change the URI from the mobile application. Is there a way to get around this? Is there a way to get the API Gateway to work while ignoring the PORT number on the request?

Thanks. I hope I have explained this well. I am happy to explain my setup further.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.