Please check the type of change your PR introduces:
[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):
What is the current behavior?
There is a but in the "scenario_state" and "scenario_hitcount" variable handlers. Whenever a lot of requests are fired for these scenarios, the wrong value might be written in the response.
What is the new behavior?
The scenario state is cached in the HttpContext (so on the HTTP request). This value will be used when written to the response instead of retrieving it from the scenario store (which might be an outdated or too new value).
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
There is a but in the "scenario_state" and "scenario_hitcount" variable handlers. Whenever a lot of requests are fired for these scenarios, the wrong value might be written in the response.
What is the new behavior?
The scenario state is cached in the HttpContext (so on the HTTP request). This value will be used when written to the response instead of retrieving it from the scenario store (which might be an outdated or too new value).
Does this introduce a breaking change?