Hi Surekha,
Generally speaking, a 408 Request Timeout error in Apigee indicates that the Apigee Message Processor did not receive the entire HTTP request payload from the client within the configured I/O timeout period. This timeout can occur when the client’s request is slow, or if there’s a network issue preventing the client from sending the complete request data within the allowed time.
Beyond that, it is hard to tell from the information provided. I do see that:
content-length: 10is provided in the request in the NOT working solution. In general, content-length should not be passed with a GET request; there should be no Body. If a client sets a non-zero content-length header in the request, and then sends no content, it’s possible that a gateway, any gateway, will just throw a 408. Solution: don’t send content-length when there is no content.- the java versions are different between the two user-agents
- and that the flows appear to be different, at least the policy list is different between the two screen shots
I’d recommend confirming there are no issues in the network path for the route that is failing.