Hey
@jsontester,
Whenever i get requests working in postman but not working in soapui/readyapi, the problem is nearly always some problem with the headers....typically content-type of authorization. If you actually think about it, the problems can only be in something fundamental like https/http/ssl/tls, or uri or payload or headers. Thats it.
The way to diagnose the problem is as mattb mentioned is to do comparison of these things but typically focus on the headers and as you mention, youve tried fiddler which is exactly what i always do.
Your last post mentions youre getting nothing in fiddler foe readyapi. Are you makiing sure youre using the proxy option in readyapi as well as postman? Remember for fiddler to capture traffic, you need to ensure you are proxying the requests via fiddler before it gets to the relevant endpoint.
Heres some instructions i found that works with soapui/fiddler. Follow these for your readyapi traffic -->
https://www.google.com/amp/s/kickingtech.com/2014/05/15/getting-fiddler-to-work-with-soapui/amp/When i get home tonight i'll run setup fiddler on mine and then confirm the simplest way of setting it up.
Also.in the meantime, if you can screenshot the RAW details of your request (and reaponse in postman) and then screenshot the same in readyapi, we should be able to identify what you need to focus on to fix this.
Cheers,
Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
