Hey
JayKrishIntriguing....ive never come across a 410 before!
Ok, so i looked through the release notes for versions 3.20.0 and 3.20.1 to see if i could see anything that jumps out that might indicate a reason why youre getting this error, but i couldnt spot anything.
Does this occur for all your SOAP test steps within your project....you get a 410 for EVERY request?
Secondly, do you get a 410 for test steps in other projects you have open in ReadyAPI!?
You have a Proxy-agent content header with the value "Oracle-Traffic-Director/12.2.1.0.0", it's a daft question i think but im guessing you are proxying your requests before they get the the relevant endpoint....is that correct? Ive seen the proxy setting switch when upgrading my ReadyAPI! version before now. I'm wondering if the proxying is helping to cause the failure to manifest.....
Have you got any test steps in the current project or others that aren't proxied at all?
Have you tried giving your SOAP service a quick poke with Postman? I could moan all day how i think Postman is naff, but one of the things it is good at is quick and easy setup if you just want to poke an API quickly. I'm curious if you get the same behaviour with Postman.
That's all i got for now i'm afraid. Perhaps one of thr other forum users will have some better ideas!
Please respond back with the results of my questions.....i'm sure we'll be able to diagnose and determine the fix once we have more info (well.....unless it's a defect).
Cheers,
Rich