khammond 02/02/24 09:53:45 Modified: docs/usermanual http-config.html Log: Added anchors. Revision Changes Path 1.6 +204 -204 jakarta-jmeter/docs/usermanual/http-config.html Index: http-config.html =================================================================== RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/http-config.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- http-config.html 23 Feb 2002 03:49:58 -0000 1.5 +++ http-config.html 24 Feb 2002 17:53:45 -0000 1.6 @@ -2,145 +2,145 @@ <!-- Content Stylesheet for Site --> - + <!-- start the processing --> - <!-- ====================================================================== --> - <!-- Main Page Section --> - <!-- ====================================================================== --> - <html> - <head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> + <!-- ====================================================================== --> + <!-- Main Page Section --> + <!-- ====================================================================== --> + <html> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> - - <title>JMeter - User's Manual: HTTP Configuration Elements</title> - </head> + + <title>JMeter - User's Manual: HTTP Configuration Elements</title> + </head> - <body bgcolor="#ffffff" text="#000000" link="#525D76"> - <table border="0" width="100%" cellspacing="0"> - <!-- TOP IMAGE --> - <tr> - <td colspan="2"> + <body bgcolor="#ffffff" text="#000000" link="#525D76"> + <table border="0" width="100%" cellspacing="0"> + <!-- TOP IMAGE --> + <tr> + <td colspan="2"> <a href="http://jakarta.apache.org";><img src="http://jakarta.apache.org/images/jakarta-logo.gif"; align="left" border="0"/></a> </td> - </tr> - </table> - <table border="0" width="100%" cellspacing="4"> - <tr><td colspan="2"> - <hr noshade="" size="1"/> - </td></tr> - - <tr> - <!-- LEFT SIDE NAVIGATION --> - <td width="20%" valign="top" nowrap="true"> - <p><strong>About</strong></p> - <ul> - <li> <a href="../index.html">Overview</a> + </tr> + </table> + <table border="0" width="100%" cellspacing="4"> + <tr><td colspan="2"> + <hr noshade="" size="1"/> + </td></tr> + + <tr> + <!-- LEFT SIDE NAVIGATION --> + <td width="20%" valign="top" nowrap="true"> + <p><strong>About</strong></p> + <ul> + <li> <a href="../index.html">Overview</a> </li> - <li> <a href="http://jakarta.apache.org/builds/jakarta-jmeter/";>Download</a> + <li> <a href="http://jakarta.apache.org/builds/jakarta-jmeter/";>Download</a> </li> - <li> <a href="../installing.html">Install</a> + <li> <a href="../installing.html">Install</a> </li> - <li> <a href="../running.html">Running</a> + <li> <a href="../running.html">Running</a> </li> - <li> <a href="../extending/index.html">Extending</a> + <li> <a href="../extending/index.html">Extending</a> </li> - <li> <a href="../changes.html">Changes</a> + <li> <a href="../changes.html">Changes</a> </li> - <li> <a href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=JMeter&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time";>Known Bugs</a> + <li> <a href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=JMeter&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time";>Known Bugs</a> </li> - <li> <a href="../license.html">License</a> + <li> <a href="../license.html">License</a> </li> - <li> <a href="../todo.html">TODO</a> + <li> <a href="../todo.html">TODO</a> </li> - </ul> - <p><strong>User Manual</strong></p> - <ul> - <li> <a href="../usermanual/index.html">Table of Contents</a> + </ul> + <p><strong>User Manual</strong></p> + <ul> + <li> <a href="../usermanual/index.html">Table of Contents</a> </li> - <li> <a href="../usermanual/intro.html">Introduction</a> + <li> <a href="../usermanual/intro.html">Introduction</a> </li> - <li> <a href="../usermanual/get-started.html">Getting Started</a> + <li> <a href="../usermanual/get-started.html">Getting Started</a> </li> - <li> <a href="../usermanual/build-test-plan.html">Building a Test Plan</a> + <li> <a href="../usermanual/build-test-plan.html">Building a Test Plan</a> </li> - <li> <a href="../usermanual/thread-group.html">Test Plan - Thread Group</a> + <li> <a href="../usermanual/thread-group.html">Test Plan - Thread Group</a> </li> - <li> <a href="../usermanual/controller.html">Test Plan - Controllers</a> + <li> <a href="../usermanual/controller.html">Test Plan - Controllers</a> </li> - <li> <a href="../usermanual/listener.html">Test Plan - Listeners</a> + <li> <a href="../usermanual/listener.html">Test Plan - Listeners</a> </li> - <li> <a href="../usermanual/timer.html">Test Plan - Timers</a> + <li> <a href="../usermanual/timer.html">Test Plan - Timers</a> </li> - <li> <a href="../usermanual/assertion.html">Test Plan - Assertions</a> + <li> <a href="../usermanual/assertion.html">Test Plan - Assertions</a> </li> - <li> <a href="../usermanual/ftp-config.html">Test Plan - FTP Config</a> + <li> <a href="../usermanual/ftp-config.html">Test Plan - FTP Config</a> </li> - <li> <a href="../usermanual/http-config.html">Test Plan - HTTP Config</a> + <li> <a href="../usermanual/http-config.html">Test Plan - HTTP Config</a> </li> - <li> <a href="../usermanual/jdbc-config.html">Test Plan - JDBC Config</a> + <li> <a href="../usermanual/jdbc-config.html">Test Plan - JDBC Config</a> </li> - <li> <a href="../usermanual/build-web-test-plan.html">Building a Web Test Plan</a> + <li> <a href="../usermanual/build-web-test-plan.html">Building a Web Test Plan</a> </li> - <li> <a href="../usermanual/build-adv-web-test-plan.html">Building an Adv. Web Test Plan</a> + <li> <a href="../usermanual/build-adv-web-test-plan.html">Building an Adv. Web Test Plan</a> </li> - <li> <a href="../usermanual/build-db-test-plan.html">Building a Database Test Plan</a> + <li> <a href="../usermanual/build-db-test-plan.html">Building a Database Test Plan</a> </li> - <li> <a href="../usermanual/build-ftp-test-plan.html">Building a FTP Test Plan</a> + <li> <a href="../usermanual/build-ftp-test-plan.html">Building a FTP Test Plan</a> </li> - <li> <a href="../usermanual/remote-test.html">Remote Testing</a> + <li> <a href="../usermanual/remote-test.html">Remote Testing</a> </li> - <li> <a href="../usermanual/best-practices.html">Best Practices</a> + <li> <a href="../usermanual/best-practices.html">Best Practices</a> </li> - </ul> - <p><strong>Community</strong></p> - <ul> - <li> <a href="http://jakarta.apache.org/site/getinvolved.html";>Get Involved</a> + </ul> + <p><strong>Community</strong></p> + <ul> + <li> <a href="http://jakarta.apache.org/site/getinvolved.html";>Get Involved</a> </li> - <li> <a href="http://jakarta.apache.org/site/mail.html";>Mailing Lists</a> + <li> <a href="http://jakarta.apache.org/site/mail.html";>Mailing Lists</a> </li> - <li> <a href="http://jakarta.apache.org/site/cvsindex.html";>CVS Repositories</a> + <li> <a href="http://jakarta.apache.org/site/cvsindex.html";>CVS Repositories</a> </li> - </ul> - </td> - <td width="80%" align="left" valign="top"> - <table border="0" cellspacing="0" cellpadding="2" width="100%"> - <tr><td bgcolor="#525D76"> - <font color="#ffffff" face="arial,helvetica,sanserif"> - <a name="$section.getAttributeValue("anchor")"><strong>4.7 HTTP Configuration Elements</strong></a> - </font> - </td></tr> - <tr><td> - <blockquote> - <p>A configuration element works closely with a Generative Controller. Although it does not send requests + </ul> + </td> + <td width="80%" align="left" valign="top"> + <table border="0" cellspacing="0" cellpadding="2" width="100%"> + <tr><td bgcolor="#525D76"> + <font color="#ffffff" face="arial,helvetica,sanserif"> + <a name="elements"><strong>4.7 HTTP Configuration Elements</strong></a> + </font> + </td></tr> + <tr><td> + <blockquote> + <p>A configuration element works closely with a Generative Controller. Although it does not send requests (except for Proxy Server), it can add to or modify requests and handle responses.</p> - <p>A configuration element is accessible from only inside the tree branch where you place the element. + <p>A configuration element is accessible from only inside the tree branch where you place the element. For example, if you place an HTTP Cookie Manager inside a Simple Logic Controller, the Cookie Manager will only be accessible to HTTP Request Controllers you place inside the Simple Logic Controller (see figure 1). The Cookie Manager is accessible to the HTTP requests "Web Page 1" and "Web Page 2", but not "Web Page 3". </p> - <p>Also, a configuration element inside a tree branch has higher precedence than the same element in a "parent" + <p>Also, a configuration element inside a tree branch has higher precedence than the same element in a "parent" branch. For example, we defined two HTTP Request Defaults elements, "Web Defaults 1" and "Web Defaults 2". Since we placed "Web Defaults 1" inside a Loop Controller, only "Web Page 2" can access it. The other HTTP requests will use "Web Defaults 2", since we placed it in the Thread Group (the "parent" of all other branches).</p> - <p><img src="../images/screenshots/http-config/http-config-example.gif" width="240" height="240" /> + <p><img src="../images/screenshots/http-config/http-config-example.gif" width="240" height="240" /> <br>Figure 1 - Test Plan Showing Accessability of Configuration Elements</br></p> - </blockquote> - </p> - </td></tr> - <tr><td><br/></td></tr> - </table> - <table border="0" cellspacing="0" cellpadding="2" width="100%"> - <tr><td bgcolor="#525D76"> - <font color="#ffffff" face="arial,helvetica,sanserif"> - <a name="$section.getAttributeValue("anchor")"><strong>4.7.1 HTTP Authorization Manager</strong></a> - </font> - </td></tr> - <tr><td> - <blockquote> - <p>The Authorization Manager lets you specify one or more user logins for web pages that are + </blockquote> + </p> + </td></tr> + <tr><td><br/></td></tr> + </table> + <table border="0" cellspacing="0" cellpadding="2" width="100%"> + <tr><td bgcolor="#525D76"> + <font color="#ffffff" face="arial,helvetica,sanserif"> + <a name="auth_manager"><strong>4.7.1 HTTP Authorization Manager</strong></a> + </font> + </td></tr> + <tr><td> + <blockquote> + <p>The Authorization Manager lets you specify one or more user logins for web pages that are restricted using Basic HTTP Authentication. You see this type of authentication when you use your browser to access a restricted page, and your browser displays a login dialog box. JMeter transmits the login information when it encounters this type of page.</p> - <p> + <p> <table border="1" cellspacing="0" cellpadding="5"> <tr><td><b>NOTE:</b> In the current release, all JMeter threads in a Thread Group use the same username/password for a given Base URL even if you create multiple users with the same Base URL in the authorization table. @@ -148,10 +148,10 @@ Test Plan, with each Thread Group having its own Authorization Manager.</td></tr> </table> </p> - <p><b>Control Panel</b></p> - <p><img src="../images/screenshots/http-config/http-auth-manager.gif" width="575" height="340" /> + <p><b>Control Panel</b></p> + <p><img src="../images/screenshots/http-config/http-auth-manager.gif" width="575" height="340" /> <br>Figure 2 - Authorization Manager Control Panel</br></p> - <p>Properties: + <p>Properties: <ul> <li>Name - Descriptive name for this element that is shown in the tree. </li> <li>Base URL - A partial or complete URL that matches one or more HTTP Request URLs. As an example, @@ -168,56 +168,56 @@ <li>Save As Button - Save the current authorization table to a file.</li> </ul> </p> - <p> + <p> <table border="1" cellspacing="0" cellpadding="5"> <tr><td><b>NOTE:</b> When you save the Test Plan, JMeter automatically saves all of the authorization table entries.</td></tr> </table> </p> - <p><b>Example</b></p> - <p><a href="../demos/AuthManagerTestPlan.jmx">Download</a> this example. In this example, we created a Test Plan on a local server that sends three HTTP requests, two requiring a login and the + <p><b>Example</b></p> + <p><a href="../demos/AuthManagerTestPlan.jmx">Download</a> this example. In this example, we created a Test Plan on a local server that sends three HTTP requests, two requiring a login and the other is open to everyone. See figure 3 to see the makeup of our Test Plan. On our server, we have a restricted directory named, "secret", which contains two files, "index.html" and "index2.html". We created a login id named, "kevin", which has a password of "spot". So, in our Authorization Manager, we created an entry for the restricted directory and a username and password (see figure 4). The two HTTP requests named "SecretPage1" and "SecretPage2" make requests to "/secret/index1.html" and "/secret/index2.html". The other HTTP request, named "NoSecretPage" makes a request to "/index.html".</p> - <p>When we run the Test Plan, JMeter looks in the Authorization table for the URL it is requesting. If the Base URL matches + <p>When we run the Test Plan, JMeter looks in the Authorization table for the URL it is requesting. If the Base URL matches the URL, then JMeter passes this information along with the request.</p> - <p> + <p> <table border="1" cellspacing="0" cellpadding="5"> <tr><td><b>NOTE:</b> You can download the Test Plan, but since it is built as a test for our local server, you will not be able to run it. However, you can use it as a reference in constructing your own Test Plan.</td></tr> </table> </p> - <p><img src="../images/screenshots/http-config/auth-manager-example1a.gif" width="292" height="205" /> + <p><img src="../images/screenshots/http-config/auth-manager-example1a.gif" width="292" height="205" /> <br>Figure 3 - Test Plan</br></p> - <p><img src="../images/screenshots/http-config/auth-manager-example1b.gif" width="572" height="341" /> + <p><img src="../images/screenshots/http-config/auth-manager-example1b.gif" width="572" height="341" /> <br>Figure 4 - Authorization Manager Control Panel</br></p> - </blockquote> - </p> - </td></tr> - <tr><td><br/></td></tr> - </table> - <table border="0" cellspacing="0" cellpadding="2" width="100%"> - <tr><td bgcolor="#525D76"> - <font color="#ffffff" face="arial,helvetica,sanserif"> - <a name="$section.getAttributeValue("anchor")"><strong>4.7.2 HTTP Cookie Manager</strong></a> - </font> - </td></tr> - <tr><td> - <blockquote> - <p>The Cookie Manager element has two functions.</p> - <p>First, it stores and sends cookies just like a web browser. If you + </blockquote> + </p> + </td></tr> + <tr><td><br/></td></tr> + </table> + <table border="0" cellspacing="0" cellpadding="2" width="100%"> + <tr><td bgcolor="#525D76"> + <font color="#ffffff" face="arial,helvetica,sanserif"> + <a name="cookie_manager"><strong>4.7.2 HTTP Cookie Manager</strong></a> + </font> + </td></tr> + <tr><td> + <blockquote> + <p>The Cookie Manager element has two functions.</p> + <p>First, it stores and sends cookies just like a web browser. If you have an HTTP Request and the response contains a cookie, the Cookie Manager automatically stores that cookie and will use if, for all future request that particular request. Each JMeter thread has its own "cookie storage area". So, if you are testing a web site that uses a cookie for storing session information, each JMeter thread will have its own session.</p> - <p>Second, you can manually add a cookie to the Cookie Manager. However, if you do this, the cookie will be + <p>Second, you can manually add a cookie to the Cookie Manager. However, if you do this, the cookie will be exposed to all JMeter threads.</p> - <p><b>Control Panel</b></p> - <p><img src="../images/screenshots/http-config/http-cookie-manager.gif" width="573" height="340" /> + <p><b>Control Panel</b></p> + <p><img src="../images/screenshots/http-config/http-cookie-manager.gif" width="573" height="340" /> <br>Figure 5 - Cookie Manager Control Panel</br></p> - <p>Properties: + <p>Properties: <ul> <li>Name - Descriptive name for this element that is shown in the tree. </li> <li>Base URL - A partial or complete URL that matches one or more HTTP Request URLs. As an example, @@ -234,24 +234,24 @@ <li>Save As Button - Save the current authorization table to a file.</li> </ul> </p> - </blockquote> - </p> - </td></tr> - <tr><td><br/></td></tr> - </table> - <table border="0" cellspacing="0" cellpadding="2" width="100%"> - <tr><td bgcolor="#525D76"> - <font color="#ffffff" face="arial,helvetica,sanserif"> - <a name="$section.getAttributeValue("anchor")"><strong>4.7.3 HTTP Header Manager</strong></a> - </font> - </td></tr> - <tr><td> - <blockquote> - <p>The Header Manager lets you add or override HTTP request headers.</p> - <p><b>Control Panel</b></p> - <p><img src="../images/screenshots/http-config/http-header-manager.gif" width="574" height="341" /> + </blockquote> + </p> + </td></tr> + <tr><td><br/></td></tr> + </table> + <table border="0" cellspacing="0" cellpadding="2" width="100%"> + <tr><td bgcolor="#525D76"> + <font color="#ffffff" face="arial,helvetica,sanserif"> + <a name="header_manager"><strong>4.7.3 HTTP Header Manager</strong></a> + </font> + </td></tr> + <tr><td> + <blockquote> + <p>The Header Manager lets you add or override HTTP request headers.</p> + <p><b>Control Panel</b></p> + <p><img src="../images/screenshots/http-config/http-header-manager.gif" width="574" height="341" /> <br>Figure 6 - Header Manager Control Panel</br></p> - <p>Properties: + <p>Properties: <ul> <li>Name - Descriptive name for this element that is shown in the tree. </li> <li>Name (Header) - Name of the request header. Two common request headers you may want to experiment with @@ -264,54 +264,54 @@ <li>Save As Button - Save the current header table to a file.</li> </ul> </p> - <p><b>Example</b></p> - <p><a href="../demos/HeaderManagerTestPlan.jmx">Download</a> this example. In this example, we created a Test Plan + <p><b>Example</b></p> + <p><a href="../demos/HeaderManagerTestPlan.jmx">Download</a> this example. In this example, we created a Test Plan that tells JMeter to override the default "User-Agent" request header and use a particular Internet Explorer agent string instead. (see figures 7 and 8).</p> - <p><img src="../images/screenshots/http-config/header-manager-example1a.gif" width="205" height="150" /> + <p><img src="../images/screenshots/http-config/header-manager-example1a.gif" width="205" height="150" /> <br>Figure 7 - Test Plan</br></p> - <p><img src="../images/screenshots/http-config/header-manager-example1b.gif" width="573" height="334" /> + <p><img src="../images/screenshots/http-config/header-manager-example1b.gif" width="573" height="334" /> <br>Figure 8 - Header Manager Control Panel</br></p> - </blockquote> - </p> - </td></tr> - <tr><td><br/></td></tr> - </table> - <table border="0" cellspacing="0" cellpadding="2" width="100%"> - <tr><td bgcolor="#525D76"> - <font color="#ffffff" face="arial,helvetica,sanserif"> - <a name="$section.getAttributeValue("anchor")"><strong>4.7.4 HTTP Proxy Server</strong></a> - </font> - </td></tr> - <tr><td> - <blockquote> - <p>The Proxy Server acts as a gateway between your web browser and the Internet (or your ISP's proxy server, if applicable). + </blockquote> + </p> + </td></tr> + <tr><td><br/></td></tr> + </table> + <table border="0" cellspacing="0" cellpadding="2" width="100%"> + <tr><td bgcolor="#525D76"> + <font color="#ffffff" face="arial,helvetica,sanserif"> + <a name="proxy_server"><strong>4.7.4 HTTP Proxy Server</strong></a> + </font> + </td></tr> + <tr><td> + <blockquote> + <p>The Proxy Server acts as a gateway between your web browser and the Internet (or your ISP's proxy server, if applicable). Instead of manually creating HTTP Request controllers, you can use a web browser. In order to do this, you need to configure your browser to use the JMeter proxy server. This proxy server listens to your browser's HTTP requests and creates the necessary HTTP Request controllers. You can place the Proxy Server element in the Thread Group. It is ok to leave this element when you run the Test Plan because it will not affect JMeter.</p> - <p>JMeter places the HTTP Request controllers in the Thread Group, or if you have a Simple Logic Controller, JMeter places + <p>JMeter places the HTTP Request controllers in the Thread Group, or if you have a Simple Logic Controller, JMeter places them there. Also, if you have a HTTP Request Defaults element, then the HTTP Request controllers will have empty fields for the default values you specified.</p> - <p> + <p> <table border="1" cellspacing="0" cellpadding="5"> <tr><td><b>NOTE:</b> If you have more than one Simple Logic Controller, JMeter adds HTTP Request Controllers to each of your Simple Logic Controllers. We plan to correct this in a future release.</td></tr> </table> </p> - <p>The Include and Exclude fields allow you to filter requests. If, for example, you leave both fields blank, then JMeter + <p>The Include and Exclude fields allow you to filter requests. If, for example, you leave both fields blank, then JMeter will record every action of your browser. This can often result in 20+ test samples being recorded for each web page (it will record all image requests, CSS files, Javascript files, etc). This is probably not desirable. The Include/Exclude fields give you some say over what gets recorded. </p> - <p>If the Include field is left empty, then all requests will "pass" the include test. If the Exclude field is left empty, then all + <p>If the Include field is left empty, then all requests will "pass" the include test. If the Exclude field is left empty, then all request will "pass" the exclude test. Once the Include field has at least one entry, then only those requests that match at least one entry will "pass" ("pass" means "be recorded"). </p> - <p>If the Exclude field is left empty, then all requests (that have passed the Include field check) will pass. If there are + <p>If the Exclude field is left empty, then all requests (that have passed the Include field check) will pass. If there are entries in the Exclude field, then any request that matches at least one entry will not be recorded.</p> - <p><b>Control Panel</b></p> - <p><img src="../images/screenshots/http-config/http-proxy-server.gif" width="398" height="288" /> + <p><b>Control Panel</b></p> + <p><img src="../images/screenshots/http-config/http-proxy-server.gif" width="398" height="288" /> <br>Figure 9 - Proxy Server Control Panel</br></p> - <p>Properties: + <p>Properties: <ul> <li>Name - Descriptive name for this element that is shown in the tree. </li> <li>Port - Port the proxy server listens for your browser's requests. The default port is 8080.</li> @@ -327,33 +327,33 @@ <li>Stop Button - Stop the proxy server.</li> </ul> </p> - <p><b>Example</b></p> - <p><a href="../demos/ProxyServerTestPlan.jmx">Download</a> this example. In this example, we created a basic Test Plan + <p><b>Example</b></p> + <p><a href="../demos/ProxyServerTestPlan.jmx">Download</a> this example. In this example, we created a basic Test Plan that tells JMeter to create a proxy server (see figure 10).</p> - <p><img src="../images/screenshots/http-config/proxy-server-example1a.gif" width="188" height="112" /> + <p><img src="../images/screenshots/http-config/proxy-server-example1a.gif" width="188" height="112" /> <br>Figure 10 - Test Plan</br></p> - </blockquote> - </p> - </td></tr> - <tr><td><br/></td></tr> - </table> - <table border="0" cellspacing="0" cellpadding="2" width="100%"> - <tr><td bgcolor="#525D76"> - <font color="#ffffff" face="arial,helvetica,sanserif"> - <a name="$section.getAttributeValue("anchor")"><strong>4.7.5 HTTP Request Defaults</strong></a> - </font> - </td></tr> - <tr><td> - <blockquote> - <p>This element lets you set default values that your HTTP Request controllers use. For example, if you are + </blockquote> + </p> + </td></tr> + <tr><td><br/></td></tr> + </table> + <table border="0" cellspacing="0" cellpadding="2" width="100%"> + <tr><td bgcolor="#525D76"> + <font color="#ffffff" face="arial,helvetica,sanserif"> + <a name="request_defaults"><strong>4.7.5 HTTP Request Defaults</strong></a> + </font> + </td></tr> + <tr><td> + <blockquote> + <p>This element lets you set default values that your HTTP Request controllers use. For example, if you are creating a Test Plan with 25 HTTP Request controllers and all of the requests are being sent to the same server, you could add a single HTTP Request Defaults element with the "Server Name or IP" field filled in. Then, when you add the 25 HTTP Request controllers, leave the "Server Name or IP" field empty. The controllers will inherit this field value from the HTTP Request Defaults element.</p> - <p><b>Control Panel</b></p> - <p><img src="../images/screenshots/http-config/http-request-defaults.gif" width="569" height="448" /> + <p><b>Control Panel</b></p> + <p><img src="../images/screenshots/http-config/http-request-defaults.gif" width="569" height="448" /> <br>Figure 11 - Request Defaults Control Panel</br></p> - <p><b>Property Descriptions:</b> + <p><b>Property Descriptions:</b> <ul> <li><b>Name</b> - Descriptive name for this controller that is shown in the tree. </li> <li><i>Web Server</i></li> @@ -381,26 +381,26 @@ </ul> </ul> </p> - </blockquote> - </p> - </td></tr> - <tr><td><br/></td></tr> - </table> - </td> - </tr> + </blockquote> + </p> + </td></tr> + <tr><td><br/></td></tr> + </table> + </td> + </tr> - <!-- FOOTER --> - <tr><td colspan="2"> - <hr noshade="" size="1"/> - </td></tr> - <tr><td colspan="2"> - <div align="center"><font color="#525D76" size="-1"><em> - Copyright © 1999-2001, Apache Software Foundation - </em></font></div> - </td></tr> - </table> - </body> - </html> + <!-- FOOTER --> + <tr><td colspan="2"> + <hr noshade="" size="1"/> + </td></tr> + <tr><td colspan="2"> + <div align="center"><font color="#525D76" size="-1"><em> + Copyright © 1999-2001, Apache Software Foundation + </em></font></div> + </td></tr> + </table> + </body> + </html> <!-- end the processing -->
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
![http://jakarta.apache.org/images/jakarta-logo.gif"](http://jakarta.apache.org/images/jakarta-logo.gif"){kind=link}