Service Virtualization

 View Only
  • 1.  In Request, unable to get : (colon) value as its a reserved character

    Posted Oct 21, 2020 11:47 AM
    Hello,

    We are expecting 2 different responses for 2 requests containing below mac ids, but its unbale to take : character, hence input till "/cms/00" is only passing in both the cases. 

    Request 1 contains data : POST /cms/00:a0:c9:14:c8:29/self-install-record
    Request 2 contains data : POST /cms/00:a0:c9:14:c8:40/self-install-record

    There is a difference in  above data but as its unable to take : (colon) character, same data is passing "/cms/00" & we are getting same response. 
    Could you please help in this case so that the entire data can be passed & hence, responses should be different.

    Note : This is being performed on DevTest Workstation

    Regards,
    Apurva


  • 2.  RE: In Request, unable to get : (colon) value as its a reserved character

    Broadcom Employee
    Posted Oct 21, 2020 12:19 PM

    What version of DevTest work station are you using?
    Also what do the logs show when it fails?
    we will need more information and details around the examples maybe post the RR pairs so that we can review and look at in a lab.



    ------------------------------
    Gene Howard
    Principal Support Engineer
    Broadcom
    ------------------------------



  • 3.  RE: In Request, unable to get : (colon) value as its a reserved character

    Broadcom Employee
    Posted Oct 21, 2020 12:32 PM
    Hi Apurva,

    What DPH's are you using? If you are using REST DPH then try make the Operation to use {URLPARM} and add the URLPARM as an argument and specify the values. You also need to have basepath as /cms/ and the REST DPH to have the URI with POST /cms/{URLPARM}/self-install-record.

    If you can share your VS MAR file, we can try also.

    Regards,
    Prema



  • 4.  RE: In Request, unable to get : (colon) value as its a reserved character

    Posted Oct 22, 2020 06:25 AM
    Hi Apurva,

    As per my understanding, REST protocol may not work in this scenario, you can go for RDM to manipulate the values and utilize the values as arguments.

    Thanks

    ------------------------------
    Regards,
    Vaibhav Jain
    Capgemini
    ------------------------------