Web Socket Open Connection sampler only takes input from one HTTP Header Manager
In contrast to the standard HTTP sampler of JMeter, the Web Socket Open Connection sampler does not merge the header specifications from all HTTP Header Manager instances in its scope. Instead, it seems to use only the header fields specified in the last sampler attached to the top most scope.
This is a severe restriction in even medium sized test plans.
See the attached test plan for an example. Here the Web Socket Open Connection sampler ignores the HTTP Header Manager that is attached to itself. In contrast, the HTTP sampler that is also contained in the test plan merges the header fields from its child Header Manager and the top level header manager.
Comments (2)
-
reporter -
repo owner Hi Jan Wilhelm,
Thanks for reporting and thanks for your clear description and reproduction scenario!
Regards
Peter - Log in to comment
Note that issue
#65probably has the same root cause: In this case the bug reporter seems to have had a top level empty HTTP Header Manager that was overriding her lower level HTTP Header manager (unexpected) instead of adding to it (expected).