Forum Discussion

yarl's avatar
yarl
New Contributor
7 years ago

Rest API call does not return XML message, but some logs, but response code is 200

HI , I am testing a REST API call from my laptop . The vpn connection to the server is established. When I run the Rest API call from SOAP UI Pro it gives 200- ok. But response in XML does not show-...
yarl's avatar
yarl
New Contributor

yes I did.

against the user I gave user@domain

against the password- I gave the password (not long password)

against the domain- I left it blank and also tried giving the domain again

but same error

nmrao's avatar
nmrao
Champion Level 3
7 years ago
may be try the other format:

domain\user as username.
  • yarl's avatar
    yarl
    New Contributor
    7 years ago

    I did try that too. Thx

    But same issue.

    The reponse is coming back with 200-OK- if issue with user/pw then it should not return 200?

     

    • richie's avatar
      richie
      Community Hero
      7 years ago
      hi,

      i had something very similar when attempting to run requests in readyapi! that failed even though the same request with the same creds worked in postman.

      i got my request working by adding in an Authorization header parameter into the GET request despite the fact that i could see the Authorization header in the requests raw details.

      so what i did.
      1.run the GET request
      2. check the raw details on the request and copy the Authorization headers value to clipboard.
      3.add in a header parm with the name 'Authorization', paste the value from clipboard into the new header's value field.
      4. save project and rerun the GET request.

      i dont know if this will fix your problem but its analagous to the problem i had and the above fixed the issue for me.

      cheers,

      richie
      • richie's avatar
        richie
        Community Hero
        7 years ago
        also relying on status codes for success is a little dodgy. i rely on an assertion for a 200 simply as a check to make sure the client and server are able to talk to each other and nothing else. you might expect a 401 or 403 for authentication failure but ig depends on your exception handling.

        ive even had instances where ive had a 200 when i submitted an invalid request! that was due to rubbish exception handling.

        cheers,

        richie