Layer7 API Management

  • Private Community
 View Only

  • 1.  Problem access response from Route via HTTP assertion

    Posted Mar 25, 2020 06:16 PM
    Hi,

    We are using V9.4, and I am using a Route via HTTP assertion.  I set the name of a var, myResponse, as the "Destination" for the assertion.

    However, when I do an Add Audit and try to output myResponse.mainpart, it is coming up empty.

    Can anyone tell me what I need to access the response (myResponse)?

    Thanks,
    Jim


  • 2.  RE: Problem access response from Route via HTTP assertion

    Broadcom Employee
    Posted Mar 25, 2020 06:24 PM
    Dear Jim,
    Assume that you refer to the var as ${myResponse.mainpart}, and the audit detail assertion is after the route assertion, and there is no error of route assertion, then the backend server may just return a response without payload.

    Regards,
    Mark
    Original Message


  • 3.  RE: Problem access response from Route via HTTP assertion

    Posted Mar 25, 2020 10:57 PM
    Hi,

    I was able to get the reasonCode, and it is a 302 (a redirect).  So where (which var) would let me see response and the location,e tc. for the redirect?

    FYI I did have the "follow redirects" checkbox in the Route assertion checked.

    Jim
    Original Message


  • 4.  RE: Problem access response from Route via HTTP assertion

    Posted Mar 25, 2020 10:58 PM
    Sorry I forgot to say that I did try ${myResponse.mainpart} and that returned empty string or nothing.
    Original Message


  • 5.  RE: Problem access response from Route via HTTP assertion
    Best Answer

    Broadcom Employee
    Posted Mar 26, 2020 01:07 AM
    Do you see anything in the ssg log?

    /opt/SecureSpan/Gateway/node/default/var/logs/ssg_0_0.log


    Regards,
    Mark
    Original Message