![]() ![]() Request is forwarded to the named target endpoint.įor example, to conditionally route messages to designated target endpoints based onĬonditions for more information. One target endpoint is available, the route rule is evaluated for its condition and, if true, the A route rule forwards a request to a particular target endpoint. Using conditional statements, you can control the target endpoint invoked by proxy endpointĬonfiguration. Message, and conditional response flow based on a (potential) HTTP status code representing an Transaction, and thus provide unconditional 'failsafe' capabilities.įor example, to execute a conditional request flow based on the HTTP verb of the request Postflows (both request and response) on ProxyEndpoints and TargetEndpoints execute for every Note that only 'named' flows can be executed conditionally. Using conditional statements, you can control the execution of named flows in ProxyEndpointsĪnd TargetEndpoints. The following example conditionally transforms XML to JSON based on the Accept Is conditional transformation of response messages, based on HTTP header or message content. Using conditional statements, you can control the enforcement of policies. You can use conditions to control behavior in the following: GET: (proxy.pathsuffix MatchesPath "/statuses") and (request.verb = "GET") Where you can use conditional statements statuses and the HTTP verb of the request is For example, theįollowing conditions evaluate to true only if the URI of the request matches You can combine conditions with AND to enforce more than one at a time. The basic structure of a conditional statement is: variable.name operator " value" Pattern matching in conditional statements, see Pattern matching withĬonditionals. TIP: For a tutorial-like topic that explains how to use This section describes how and where to use conditional statements with Edge. Conditional statementsĪre boolean and always evaluate to true or false. On variables, which are evaluated by the Apigee Edge processing pipeline. View Apigee X documentation.Ĭonditions enable API proxies to behave dynamically at runtime. For any non-primitive objects x and y which have the same structure but are distinct objects themselves, all of the above forms will evaluate to false.You're viewing Apigee Edge documentation. Note that the distinction between these all have to do with their handling of primitives none of them compares whether the parameters are conceptually similar in structure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |