This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
I would trace the proxy when it is being invoked as a service callout
then as my next step. Likely a header is getting stripped or some other
key variable is being omitted in the callout.
If the path is required to be different then the loadbalancer tag is not
going to work. When you say you don't have Apigee access, I presume you
mean you can not change KVM values. Is that correct? If that is the
case, then you could potentially util...
Typically this indicates that an underlying resource required for
establishing your instance is not available due to exceeding a quota
limit. Given this is in the step where you are establishing Access
Routing this may mean you are unable to create t...
The LoadBalancer is intended to balance traffic between identical
origins, it does not support dynamic changes to the path. In my
experience the best approach to this type of conditional routing is
accomplished using javascript to set a variable for ...