Tools, FAQ, Tutorials:
'{{...}}' Liquid Codes in 'set-body' Policy Statement
How to use "{{...}}" Liquid Codes in "set-body" Policy Statement?
✍: FYIcenter.com
The "{{...}}" Liquid Codes in "set-body" Policy Statement allows you
to insert object properties of the original request in JSON format
and object properties of the built-in "context" object.
For example, the following "set-body" builds an XML document as the Azure request body by converting JSON object properties from the original client request body to XML elements:
<set-body template="liquid"> <soap:Envelope xmlns="http://fyicenter.com/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <GetOrders> <Customer>{{body.getOrders.customer}}</Customer> </GetOrders> </soap:Body> </soap:Envelope> </set-body>
You can also access the following properties of the built-in object "context" using Liquid codes "{{...}}":
context. Request. Url. Scheme Host Port Path Query QueryString ToUri ToString Method OriginalMethod OriginalUrl. ... IpAddress MatchedParameters HasBody ClientCertificates Headers Response. StatusCode Method Headers
For more information on "{{...}}" Liquid codes, see Liquid code Website.
Â
⇒ Policy to Control Backend Service
⇠'set-body' Azure API Policy Statement
2017-12-04, 3718👍, 0💬
Popular Posts:
What is EPUB 2.0 Metadata "dc:creator" and "dc:contributor" elements? EPUB 2.0 Metadata "dc:creator"...
FYIcenter JSON Validator and Formatter is an online tool that checks for syntax errors of JSON text ...
Where to find tutorials on Microsoft Azure services? Here is a large collection of tutorials to answ...
How to troubleshoot the Orderer peer? The Docker container terminated by itself. You can follow this...
How to use the "send-one-way-request" Policy statement to call an extra web service for an Azure API...