jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pmoua...@apache.org
Subject svn commit: r1828836 - in /jmeter/trunk/xdocs: changes.xml usermanual/component_reference.xml
Date Tue, 10 Apr 2018 17:03:44 GMT
Author: pmouawad
Date: Tue Apr 10 17:03:44 2018
New Revision: 1828836

URL: http://svn.apache.org/viewvc?rev=1828836&view=rev
Log:
Bug 62252 - HTTP header merging logic does not correspond to the documentation
Bugzilla Id: 62252

Modified:
    jmeter/trunk/xdocs/changes.xml
    jmeter/trunk/xdocs/usermanual/component_reference.xml

Modified: jmeter/trunk/xdocs/changes.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/changes.xml?rev=1828836&r1=1828835&r2=1828836&view=diff
==============================================================================
--- jmeter/trunk/xdocs/changes.xml [utf-8] (original)
+++ jmeter/trunk/xdocs/changes.xml [utf-8] Tue Apr 10 17:03:44 2018
@@ -185,6 +185,7 @@ this behaviour, set <code>httpclient.res
 <h3>Timers, Assertions, Config, Pre- &amp; Post-Processors</h3>
 <ul>
     <li><bug>61664</bug>HTTP Authorization Manager : Digest works only
with legacy RFC 2069 , RFC 2617 is not implemented. Contributed by Ubik Load Pack (support
at ubikloadpack.com)</li>
+    <li><bug>62252</bug>HTTP header merging logic does not correspond to
the documentation</li>
 </ul>
 
 <h3>Functions</h3>

Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1828836&r1=1828835&r2=1828836&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Tue Apr 10 17:03:44 2018
@@ -3861,9 +3861,9 @@ but if the button is on, a later element
 <p>The Header Manager lets you add or override HTTP request headers.</p>
 <p>
 <b>JMeter now supports multiple Header Managers</b>. The header entries are merged
to form the list for the sampler.
-If an entry to be merged matches an existing header name, it replaces the previous entry,
-unless the entry value is empty, in which case any existing entry is removed.
-This allows one to set up a default set of headers, and apply adjustments to particular samplers.

+If an entry to be merged matches an existing header name, it replaces the previous entry.
+This allows one to set up a default set of headers, and apply adjustments to particular samplers.
+Note that an empty value for a header does not remove an existing header, it justs replace
its value.
 </p>
 </description>
 



Mime
View raw message