Layer7 API Management

Expand all | Collapse all

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

Jump to Best Answer
  • 1.  respone.mainpart is null when the HTTP reason code is not 200

    Posted 11-16-2017 07:33 AM

    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.  



  • 2.  Re: respone.mainpart is null when the HTTP reason code is not 200
    Best Answer

    Posted 11-16-2017 09:33 AM

    Hi Arun,

     

    Does the policy fail? You may want to check this setting in the route assertion.

     

    mainpart: 524 A timeout occurred 
    code: 524

     

     

    Regards,

    Joe