AnsweredAssumed Answered

respone.mainpart is null when the HTTP reason code is not 200

Question asked by a.b.viswanathan on Nov 16, 2017
Latest reply on Nov 16, 2017 by dasjo02

I have a route to assertion where i route the default request to back end server, everything works fine, I am able to read the response using ${response.mainpart} when the ${httpRouting.reasonCode} returns 200;. 

 

But the the ${httpRouting.reasonCode} is not 200, I am not able to read the ${response.mainpart} which seems to be null. Is there any way to read the response. The client is sending some custom response which they want to display in mobile app. I cant maintain all possible error codes in Layer 7.  

Outcomes