https://issues.apache.org/bugzilla/show_bug.cgi?id=54005
Sebb <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #2 from Sebb <[email protected]> --- Documentation says that adding a Header Manager controls the responses such as X-ResponseStatus. However, this is not strictly true. At present the mirror server only looks for settings such as X-ResponseStatus in the headers it receives. It does not check the contents of any Header Manager that may be added to the workbench. The only way to tell the server return the headers is to add the Header Manager to the client request. Adding a Header Manager to the Mirror Server does not work, contrary to how the docs can be read. This is not particularly flexible - for example it cannot easily be used with browsers, only with other JMeter test elements. I suspect it will be quite difficult to add, as Header Managers need special handling in the test plan. Also again it is not particularly flexible. It would probably be a lot easier to just add a table of settings to the Mirror Server GUI. There should be a table for arbitrary http headers to be added verbatim. The other features (length/response code etc) would need separate fields. For compatibility, the X-headers should still be processed if found in the request. Alternatively, the docs need to be clarified. -- You are receiving this mail because: You are the assignee for the bug.
