We have an issue in our Org where a client ip, from a computer based in Ireland gets a 404 returned. The request is successfully hitting the external API, however when it's routed to the internal api, it fails with a 404. If we add a host entry with an ip located in the US, the request works. Is Apigee's internal routing based on the client's region?
Here is the request sequence:
External API -> internal api -> internal api -> target
The request from the first internal api to the second internal api is failing with a 404. However is we add the the ip and dns name to our hostfile, the internal calls work without a problem.
Why would an internal api that calls another internal api have a routing issue based on the location of the client request?
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |