Service Virtualization

Expand all | Collapse all

How to make Virtual HTTPS Responder to send response to different endpoint?

Jump to Best Answer
  • 1.  How to make Virtual HTTPS Responder to send response to different endpoint?

    Posted 03-01-2018 08:28 AM

    Below is my scenario

     

    Listener step will receive the request from url1. Request will be routed to response selection step and now the responder step should send the response back to url2. How to make responder step to send response to url2 instead of url1?

     

    I tried adding an Web Service Execution(XML) step after response selection step and provided the url2 in the endpoint and provided the {{lisa.vse.response}} in raw XML tag. Getting below error in Web Service Execution(XML) step.

     

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <soapenv:Fault>
    <faultcode xmlns:ns1="http://xml.apache.org/axis/">ns1:HTTP</faultcode>
    <faultstring>(403)CoachingSessionExceeded</faultstring>
    <detail>
    <string>return code: 403

     

    Kindly provide me the solution.



  • 2.  Re: How to make Virtual HTTPS Responder to send response to different endpoint?
    Best Answer

    Posted 03-01-2018 11:47 AM

    Hi,

        Your approach is good, but check your payload, I think you only need the body of lisa.vse.response.

                                                    Thanks,

    Vish



  • 3.  Re: How to make Virtual HTTPS Responder to send response to different endpoint?

    Posted 03-02-2018 07:13 AM

    Thanks. Will check on it.



  • 4.  Re: How to make Virtual HTTPS Responder to send response to different endpoint?

    Posted 03-02-2018 04:43 PM

    The error code in the SOAP fault seem to indicate a permission error. For example, a google search on error code 403 (for HTTP): 

    "403 Forbidden or No Permission to Access. A 403 Forbidden error means that you do not have permission to view the requested file or resource. While sometimes this is intentional, other times it is due to misconfigured permissions. The top reasons for this error are permissions or .htaccess error"

     

    Have you confirmed that you have setup your payload correctly? Do you have to provide some authentication in the HTTP headers?