Getting response code in error rule

Hello Shahar,

Thanks for your comments. Yes indeed I am logging different error cases from an error rule with “Process Backend Errors" option turned off.

So there are ways for getting the response code in an error rule. However I am not dismissing that you are facing an issue here. I will send you an email to arrange a meeting so that we can further discuss.

Thank you.

Ulas

Hi,

I'm sorry but this is simply untrue.

I've tested it before and all I get in "hm.response.statusCode" and in "hm.response.reasonPhrase" is undefined.

It does work fine when "Process Backend Errors" option is turned on and you get the response rule invoked, but if this option is turned off, you find yourself in the error rule with no data.

You can see in the case that is attached to this idea my example. I have no idea, Ulas, I did you got the desired results.

Are you sure you logged these values from the error rule? and that the "Process Backend Errors" option was turned off? because that's just not working for me.

Thanks,

Shahar.

Hello,

When the response comes from the server, you get access to fields in the response headers in GatewayScript with assignment statements in original, current, or response headers.

…

var hm = require('header-metadata');

var statuscode = hm.original.statusCode;

var reasonphrase = hm.original.reasonPhrase;

….

https://www.ibm.com/docs/en/datapower-gateway/10.5.0?topic=module-status-codes-reason-phrases

Or in XSLT you can use

<xsl:value-of select="dp:http-response-header('x-dp-response-code')"/>

The x-dp-response-code special code is a protocol response code. This special code is not a response header, but contains the protocol-specific response code.

https://www.ibm.com/docs/en/datapower-gateway/10.5.0?topic=functions-dphttp-response-header

Then you can log or do something else according to your error handling logic... below screenshot shows an example of logging the response code logged in an error rule

Thanks

Ulas