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, 299👍, 0💬
Where to find tutorials on how to create Your Own Functions in PHP? A collection of tutorials to ans...
How To Control Horizontal Alignment in Table Cells? By default, text in all table cells are aligned ...
How to install .NET Framework in Visual Studio Community 2017? I have the Visual Studio Installer in...
How to start Visual Studio Command Prompt? I have Visual Studio 2017 Community version with Visual C...
How To Connect to MySQL from a PHP Script in PHP? If you want access the MySQL server, you must crea...