How to capture 413 error in Apigee?
Can you please suggest to me how I can capture a 413 error in Apigee? I added the below conditions in proxy <faultRule>. Tried all 3 conditions, none of them worked.
error.errorcode = "protocol.http.TooBigBody"
error.state.code = 413
error.class="com.apigee.errors.http.user.requestTooLarge"
<FaultRule name="Too Large Request">
<Condition>(error.errorcode = "protocol.http.TooBigBody")</Condition>
<Step>
<Name>RF-TooLargeRequest</Name>
</Step>
</FaultRule>
Tried the same condition in <DefaultFaultRules>, it still didn't work. Appreciate your suggestion.
Try this - error.status.code=413.
I assumed the 413 error is from backend service. Looks like the 413 error happening in proxy.
Check the value of the flow variable fault.name in trace & add condition like below.
<Condition>(fault.name Matches "<value of fault.name>")</Condition>
it is happening in proxy, not even going to backend. I am not sure about the fault.name for this error, not able to find this in trace.
Hi @Soma Ghosh
In your proxy can you add javascript policy under FaultRules section. In that Javascript code can you add following lines.
print("Faultname " + context.getVariable('fault.name'));
print("Error Status Code " + context.getVariable('error.status.code'));
print("Error State " + context.getVariable('error.state'));
Start Tracing the proxy and make the call. If error is coming from proxy you will see values being populated for above flow variables.
Try and reproduce the error and see what's printed on you trace output from all transaction window.
Within FaultRules I am not able to print the 413 error status code.
I created a separate test proxy and added DefaultFaultRules with <AlwaysEnforce> as 'true'.
In DefaultFaultRules I am able to print fault.name='TooBigBody' and error.status.code=413.
Any idea why I am not able to capture the error in FaultRules?
@Soma Ghosh
According to the documentation: A DefaultFaultRule acts an exception handler for any error that is not explicitly handled by FaultRule.
If you are interested in this topic
Couple of Apigee community page link explaining error handling in quite detail.
https://community.apigee.com/articles/23724/an-error-handling-pattern-for-apigee-proxies.html
https://community.apigee.com/articles/47312/an-improved-pattern-for-fault-handling.html
Also link to 4MV4D by @Anil Sagar @ Google explains basics of Default Fault rule.
In Summary for your above example to capture 413 you need to use DefaultFaultRule as you tried out in test proxy.
