We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More

Forum Discussion

SagarShroff's avatar
SagarShroff
Occasional Contributor
10 years ago
Solved

Empty Http response with 200 status code

Hi   I facing 1 issue in my tests, on executing the http request via 'Verify Scenario', the request returns appropriate response. But on executing the same http request via 'Tests', the request ret...
  • SagarShroff's avatar
    SagarShroff
    10 years ago

    So the solution was, there is a global settings under logging to store full headers and bodies. And it was the default settings. The main problem is that it was logging both headers and bodies in 'Verify Scenario' but when executed via tests then it was logging as per configuration which led to confusion. Please fix it.

SagarShroff's avatar
SagarShroff
Occasional Contributor
10 years ago

So the solution was, there is a global settings under logging to store full headers and bodies. And it was the default settings. The main problem is that it was logging both headers and bodies in 'Verify Scenario' but when executed via tests then it was logging as per configuration which led to confusion. Please fix it.

RyanHeidorn's avatar
RyanHeidorn
Icon for Staff rankStaff
10 years ago

Hi SagarShroff,

 

Indeed you are correct - it looks as though verifying a scenario will always store full request bodies, regardless of the settings configuration. I have reported this bug and we look forward to fixing it in a future release.

 

Thanks for reporting it!

Best,

  • AlexKaras's avatar
    AlexKaras
    Community Hero
    10 years ago

    RyanHeidorn: Hi Ryan,

     

    I probably missed the point of SagarShroff, but for me the way LoadComplete works seems to be the logical and expected:

    -- Scenario verification is done on behalf of single user and complete headers and bodies are logged in order to make it possible to thoroughly verify that all dynamic parameters were provided as expected;

    -- When scenario is executed, only headers are logged by default (in order to save disk space and for performance reasons, I guess);

    -- If something wents wrong during load test run and information from headers is not enough to figure-out the reason of the problem, one can turn on complete logging to get more information.

     

    Did I missed something?

     

    The only thing that possibly can be improved here is to add a message (label) to the bodies log panel to make it evident to the user that the panel is empty not because the body does not contain data but because the logging was disabled in the test run settings.

     

    Comments are really welcome.

    • RyanHeidorn's avatar
      RyanHeidorn
      Icon for Staff rankStaff
      10 years ago

      AlexKaras Hi Alex,

       

      Good intuition. I spoke with our developers and this indeed is the expected behavior, for exactly the reasons you listed. I had not noticed this behavior before, as I almost always keep full logging on. So, you haven't missed anything!

       

      Your idea about a message in the bodies log panel is a very good one. I'm going to suggest this directly to our developers.

       

      Thanks for the insight!

      • AlexKaras's avatar
        AlexKaras
        Community Hero
        10 years ago

        Hi Ryan,

         

        Great. Thank you a lot for both, prompt reply with the motivated confirmation and acceptance of improvement request.

        Much appreciated!