Layer7 API Management

Expand all | Collapse all

${httpRouting.reasonCode} does not get populated for an Routing Failure

Jump to Best Answer
  • 1.  ${httpRouting.reasonCode} does not get populated for an Routing Failure

    Posted 01-25-2017 01:53 PM

    Hi,

     

    We are trying to test for time out and invalid URL and other  httpRouting.reasonCode listed but observed that the value returned in such scenario is not set even such condition is simulated. Using L7 9.1

     

    Any one face similar issues ? please advice  . None of values are getting populated

     

    Returns one of the following reason codes when the HTTP routing fails:

    • -1 (Host Not Found): The Server referenced in the URL (for example, nonexistentServer.l7tech.com) cannot be reached. This code can be returned if either the host does not exist or the host is simply down.
    • -2 (Bad URL): The URL is incorrect. This could be caused by an incorrect character such as "#".
    • -3 (Connection timeout): An initial message was sent to the URL but no response was received before the connection timeout expired. The connection timeout value is defined in the assertion properties.
    • -4 (Read timeout): One of packets being received from the URL took longer than the read timeout value to be received. The read timeout value is defined in the assertion properties.
    • -5 (Undefined): An unknown type of error has occurred.


  • 2.  Re: ${httpRouting.reasonCode} does not get populated for an Routing Failure
    Best Answer

    Posted 01-25-2017 03:53 PM

    Hi Abiram,

     

    Could you share a sample of the policy you are using? I would check the ordering of your statements. If the route times out and you are not nested inside an 'At least One' assertion the next line will not execute, I have provided a snippet of my sample below.

     

     

    Regards,

    Joe