Bug 54005 - HTTP Mirror Server : Add special headers "X-" to control Response status and response content
HTTP Mirror Server : Add special headers "X-" to control Response status and ...
Status: REOPENED
Product: JMeter
Classification: Unclassified
Component: HTTP
2.8
All All
: P2 enhancement (vote)
: ---
Assigned To: JMeter issues mailing list
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2012-10-14 13:43 UTC by Philippe Mouawad
Modified: 2013-08-22 11:39 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2012-10-14 13:43:23 UTC
It can be useful to have more control on response when using Mirror Server.
I propose to add:
- X-ResponseStatus to control status of response
- X-ResponseLength to control size of response
Comment 1 Philippe Mouawad 2012-10-14 13:53:54 UTC
Date: Sun Oct 14 13:52:00 2012
New Revision: 1398084

URL: http://svn.apache.org/viewvc?rev=1398084&view=rev
Log:
Bug 54005 - HTTP Mirror Server : Add special headers "X-" to control Response status and response content
Bugzilla Id: 54005

Modified:
    jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/control/HttpMirrorThread.java
    jmeter/trunk/xdocs/changes.xml
    jmeter/trunk/xdocs/usermanual/component_reference.xml
Comment 2 Sebb 2013-08-22 11:39:49 UTC
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.