CODEWITHSUNDEEP
apigee
mparaz
mparaz

Reputation: 2069

How to handle Apigee error case when query parameter checking in proxy

I have the following. The parameter "g" is allowed to be "on" or "off", otherwise go to an error policy. However, the exception case is never called. Instead, the "on" case is called if something that is not "on" or "off" is passed as "g". Why is that? Or, is there a better way of expressing this?

<PreFlow name="PreFlow">
    <Request>
        <Step>
            <Condition>message.queryparam.g := "on"</Condition>
            <Name>GOn</Name>
        </Step>
        <Step>
            <Condition>message.queryparam.g := "off"</Condition>
            <Name>GOff</Name>
        </Step>
        <Step>
            <Condition>!((message.queryparam.g := "off") || (message.queryparam.g := "on"))</Condition>
            <Name>GError</Name>
        </Step>
    </Request>

Upvotes: 0

Views: 1592

Answers (3)

Naveen Singh
Naveen Singh

Reputation: 21

If you have multiple conditional checks try using javascritp.In the java script check the various conditions and set flag.And in the flow based on the value of flag execute the required policy.But for the above instance ,as Michael pointed out , the conditions should work as expected.

Upvotes: 1

Mike Dunker
Mike Dunker

Reputation: 1990

I agree with Michael, the code as shown is correct.

Thinking about possible issues that could cause this code to not work as expected:

  1. Make sure that the names are correct inside your GOn, GOff, and GError policies. (If you are working offline, the name of the file has nothing to do with which policy gets called.) For example, the outer element of the GOn policy should look something like

    <AssignMessage name="GOn">

  2. If GOn uses AssignMessage to modify message, you might blow away the g query parameter during a step, and your later checks might fail. If you are modifying the message, store message.queryparam.g into a different variable before you do your checks.

  3. I would use the trace tool and a tool like Postman to see what is happening for each request. The trace should tell you the variables that have been checked and their values, and you might be able to see where you are going wrong.

Upvotes: 1

Michael Russo
Michael Russo

Reputation: 628

I just tested your conditions and they work properly. If the request has the following query parameter values:

g=on or g=ON, the GOn policy will execute.

g=off or g=OFF, the GOff policy will execute.

g={anythingelse}, the GError policy will execute.

The := operator is the equals case-insensitive operator. How are you determining that the conditions are not working? Using your example, I made each of the policies a RaiseFault with a different fault response payload. This allowed me to verify which policy was executed depending on the value of g.

Upvotes: 1

Related Questions