Service Virtualization

  • 1.  Issue in SSL recording in portal

    Posted Aug 17, 2018 07:29 AM

    Hi Listeners,

     

    I'm trying to record  a SSL conversation b/w the application and backend using portal. The protocol is https.

     

    I setup the recorder and in the application service config, I have given plain http endpoint of the recorder and b/w the recorder and the backend, I have enabled the SSL. In the server endpoint, I have provided the https endpoint and the recorder is able to connect to it as it turns Green.

     

    In the select certificate presented to server, I provided the certificate details. So the recorder is sending https communication to the server. When I do the recording , I could able to see a hit coming from the application, but the response getting captured is as below. 

     

    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <html><head>
    <title>404 Not Found</title>
    </head><body>
    <h1>Not Found</h1>
    <p>The requested URL XXXX was not found on this server.</p>
    <hr>
    <address>IBM_HTTP_Server at *** Port 12345</address>
    </body></html>

     

    However, If I try to hit the server endpoint standalone from SoapUI after loading the certs, I'm able to get the response.

     

    I have also checked the Do not modify host header parameter received from client but not sure why I'm not able to record the traffic. I checked the recorded msg and all the header parameters are intact. 

     

    Any help is much appreciated.

     

    Regards,

    Shivakumar.



  • 2.  Re: Issue in SSL recording in portal

    Broadcom Employee
    Posted Aug 20, 2018 01:16 AM

    Hi,

     

    What version of DevTest are you using?
    Did you try to record the same conversation in DevTest Workstation?

     

    Thank you,



  • 3.  Re: Issue in SSL recording in portal
    Best Answer

    Posted Aug 23, 2018 04:24 AM

    Hi,

     

    The issue is fixed now.  When I unchecked the "Do not Modify the header parameters from the client", it was working fine now. I could able to record the transaction traffic. Not sure why enabling that is causing the above stated issue though?

     

    Thanks and Regards,

    Shivakumar.