Solved: IgnoreUnresolvedVariables not working as expected ... - Page 2

pankajrai9026 · 03-10-2021 05:30 AM

The IgnoreUnresolvedVariables option is not working as per Apigee documentation.

If we are not setting the value of this field, it should take false as default value but when we are extracting any value from header , URI, query or formparam , and the particular field we are not passing in request then also this policy executing successful and creating variable with that particular name.

But in case of extracting value from json payload or XML payload, it's working as expected as per Apigee documentation.

Can anyone please help on this.@dino-at-google

API-Evangelist

FYI: Check if it matches your question.

Issue with the Extract Variable policy, specifically in the IgnoreUnresolvedVariables setting. If the element is missing, it used to ignore and continue, but post upgrade to newer versions, if the element doesn’t exist, it fails.

This is likely due to an issue which was present in Private Cloud version 4.19.06.07. Specifically, when an XML variable was not resolved via an XPath expression, the ExtractVariables policy continued to execute in the proxy. This occurred even when the IgnoreUnresolvedVariables element or the continueOnError attribute were set to false.

This issue appears to have been resolved in 4.50.00 and is now working as intended.

View solution in original post

IgnoreUnresolvedVariables not working as expected within ExtractVariables POLICY