Forum Discussion
Hi,
Thanks for the suggestions. Yes, there are other headers missing. I am sure they are removed in the same place as the Auth header.
> Could you try creating a new request for the method and copy the JSON data?
Yes
I have several PUT methods in my solution, all of which exhibit the same behaviour. Steps 2 & 3 show a PUT request that does not require a body. It works. Step 3, pics 3 & 4 show a request that *should* have a body being sent without one; with expected result. I did in each case what you asked, before I posted, though I guess I did not post those results.
So - a new request for the method, creatively named "CreateUser_2" with the same problem:
> In the service viewer did you assign the Endpoint details to all requests and test requests?
I'm not sure what this means - I thought that adding the Service Endpoints for my "base url" would cover all URLs based on that value:
The Auth Header is added to all requests by adding this (aside from the PUT requests as discussed). I should surely not have to list every single endpoint I want the Auth Header added to?
> And in the request editor Auth tab did you add Basic authorization type?
No, the idea is that it should be automatically added at a higher level, ie, to all requests, not at the individual level. I want all requests to carry the Auth headers
I've moved on and used Wiremock to do the calls I need; I was hoping that I could use SOAP because ultimately the tests belong to the QA team; their test suite is written with SOAPUI but this bug was a deal-breaker for me (I am a developer)
If you want to check it out, here's my project. You'll need a default installation of RabbitMQ running, and create the admin user.
Related Content
- 2 years agogalfven
- 10 months agoashutosh01
- 4 years agojodydowling
Recent Discussions
- 2 days agoemoya
- 2 days agoMyBalanceNow