Policy Hierarchy and 'base' Statement
What are the relations among API policies defined at product level, API level, and operation level?
Azure API Management allows you to define policies at 3 levels:
The "base" Policy statement allows you to call the same policy block in the next upper level of the policy hierarchy. The "base" policy statement is a simple <base/> with no attributes and no content.
For example, the following "inbound" policy defined at the operation level will call the "inbound" policy defined at the operation level.
<inbound> <base /> ... operation own policy statement </inbound>
The following "backend" policy defined in an operation will not call the API "backend" policy. Azure API management will not forward this operation to any backend system, because is have no policy statement:
Assuming we have the following 3 policies defined:
Operation inbound policy: <inbound> <base /> <!-- calling the API inbound policy <trace source="DEBUG">Hello from Operation Z!</trace> </inbound> API inbound policy: <inbound> <base /> <!-- calling the product inbound policy <trace source="DEBUG">Hello from API Y!</trace> </inbound> Product inbound policy: <inbound> <trace source="DEBUG">Hello from Product X!</trace> </inbound>
When Azure API management process the inbound request from a client system, it will produce DEBUG trace messages in order listed below:
Hello from Product X! Hello from API Y! Hello from Operation Z!
2018-03-10, 1261👍, 0💬
How To Control Vertical Alignment? By default, text in all table cells are aligned to the top vertic...
Can You Add Values to an Array without Keys in PHP? Can You Add Values to an Array with a Key? The a...
How to use the "find-and-replace" Policy Statement for an Azure API service operation? The "find-and...
Where to find tutorials on Microsoft Azure services? Here is a large collection of tutorials to answ...
How to access Request body from "context.Request.Body" object in Azure API Policy? Request body is t...