jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1544797 - /jmeter/trunk/xdocs/usermanual/component_reference.xml
Date Sat, 23 Nov 2013 13:51:01 GMT
Author: sebb
Date: Sat Nov 23 13:51:00 2013
New Revision: 1544797

Document DNS wildcard matching


Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Sat Nov 23 13:51:00 2013
@@ -5877,7 +5877,11 @@ Both Chrome and Internet Explorer use th
         <property name="Name" required="No">Descriptive name for this element that
is shown in the tree.</property>
         <property name="Port" required="Yes">The port that the HTTP(S) Test Script
Recorder listens to.  8080 is the default, but you can change it.</property>
         <property name="HTTPS Domains" required="No">List of domain (or host) names
for HTTPS. Use this to pre-generate certificates for all servers you wish to record.
-        For example, *
+        <br/>
+        For example, *,*
+        <br/>
+        Note that wildcard domains only apply to one level,
+        i.e. matches * but not *
         <property name="Target Controller" required="Yes">The controller where the
proxy will store the generated samples. By default, it will look for a Recording Controller
and store them there wherever it is.</property>
         <property name="Grouping" required="Yes">Whether to group samplers for requests
from a single "click" (requests received without significant time separation), and how to
represent that grouping in the recording:

View raw message