Hey KayleighH
I don't know the answer from personal experience here, but I'm going to use logic to answer the question.
the answer to question i s "yes", and the second part of answer is "use fiddler to capture existing traffic that works, then tailor your ReadyAPI requests you've setup to emulate the web requests"
OK - reasons for my answers above.
If you think about it - the listening endpoint is NOT cognizant of the application that is sending the request unless there is a User-Agent header.
If you think about the contents of a web request - you have a payload, a URL (with URI/Query/Matrix parms) and Header parms. That's it - nothing more than that - so as long as you are emulating a working request by reproducing the setup in ReadyAPI to match a working request - then it will be successful.
Your listening endpoint doesn't know it's ReadyAPI! or SOATest or Postman or Katalon or JMeter or whatever (well - it does with Postman cos it always adds in the User-Agent header by default) - but unless you add in the User-Agent header - the endpoint has no idea what the source of the actually request is.
SO - I suspect if your ReadyAPI requests aren't working correctly - it's likely the Headers aren't set as the listening endpoint expects - so likely the User-Agent, but there could be some additional Headers expected that you're not including in your ReadyAPI request.
In this case I'd use Fiddler to capture the genuine traffic (capturing the RAW of the Request) and then i'd update my ReadyAPI request's Header listing (and values) to reproduce exactly the genuine web request that works.
the above is a total guess on my part - but using logic? I think it might be the right answer...... 🙂
Cheers,
Rich
