Hi - we are trying to do some work in edge w/ caching and we are seeing a rather interesting behavior:
the request.uri is being defined differently in the REQUEST and RESPONSE flows - hence the cache key is being defined differently and response cache misses are happening when they should not be.
lets say a request is being made to the following:
https://myhostname/myproxy/api/somepath?xy7
In the REQUEST flow the REQUEST URI will show up as:
/api/somepath?xy7
in the RESPONSE flow the REQUEST URI will show up as :
myproxy/api/somepath?zxy7
This is making us see inconsistent results out of Apigee.
LinkedIn
Twitter
