on ‎2020 Apr 24 11:02 AM
I have a box standard API Proxy where I can call the endpoint using the GET verb. The path suffix looks like below:
/order/58
The resource is setup as follows:

The problem I'm having is with the DefaultFaultFlow policy. When enabled, the policy always gets triggered, when turned off the endpoint successfully makes the SOAP call to my backend server and returns the results for the passed order id.
I suspect it has something to do with the pattern matching of the URL. The condition string for the policy is:
proxy.pathsuffix MatchesPath "/order/" OR proxy.pathsuffix MatchesPath "/order//**" OR proxy.pathsuffix MatchesPath "/order/(**" OR proxy.pathsuffix MatchesPath "/order/{orderId}" OR proxy.pathsuffix MatchesPath "/order/{orderId}/**" OR proxy.pathsuffix MatchesPath "/order/{orderId}(**"
The error returned, which doesn't really tell me much is:
{
"fault": {
"faultstring": "Raising fault. Fault name : defaultRaiseFaultPolicy",
"detail": {
"errorcode": "steps.raisefault.RaiseFault"
}
}
}
I've searched around for working examples, but so far I'm stuck. Does anyone have any ideas what the issue could be?
Request clarification before answering.
I've moved the AssignMessage policy which holds my SOAP payload, over into the PostFlow section of the proxy. Now, the GET verb is correctly presented and the flow conditions fire as they should. Hope that helps someone out in the future!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 9 | |
| 7 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.