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, 274👍, 0💬
How To Use Different Markers on Ordered List Items? By default, browsers will use decimal numbers as...
Why Do You Need to Filter Out Empty Files in PHP? When you are processing uploaded files, you need t...
How To Get All the Values Out of an Array in PHP? Function array_values() returns a new array that c...
How To Support Hidden Form Fields in PHP? Hidden fields are special fields in a form that are not sh...
How To Remove Slashes on Submitted Input Values in PHP? By default, when input values are submitted ...