...
If the request uses a technique called "URL Rewriting" to maintain sessions, then see section 6.1 Handling User Sessions With URL Rewriting for additional configuration steps.
Control Panel
http://jakarta.apache.org/jmeter/images/screenshots/gen-controller/http-request.png
Parameters
Attribute | Description | Required |
Name | Descriptive name for this controller that is shown in the tree. | No |
Server | Domain name or IP address of the web server. | Yes |
Port | Port the web server is listening to. | No (defaults to 80) |
Protocol | HTTP or HTTPS. | Yes |
Method | HTTP GET or HTTP POST. | Yes |
Redirect Automatically | Set the http connection to automatically follow redirects. If set, the redirects will not appear as samples, as JMeter never sees them. | No |
Follow Redirects | If set, the JMeter sampler will follow redirects, which will thus appear as samples. | No |
Use KeepAlive | JMeter sets the Connection: keep-alive header. This does not work properly with the default HTTP implementation, as connection re-use is not under user-control. It does work with the Jakarta httpClient implementation. | No |
Path | The path to resource (for example, /servlets/myServlet). If the resource requires query string parameters, add them below in the "Send Parameters With the Request" section. | Yes |
Send Parameters With the Request | The query string will be generated from the list of parameters you provide. Each parameter has a name and value , the options to encode the parameter, and an option to include or exclude an equals sign (some applications don't expect an equals when the value is the empty string). The query string will be generated in the correct fashion, depending on the choice of "Method" you made (ie if you chose GET, the query string will be appended to the URL, if POST, then it will be sent separately). Also, if you are sending a file using a multipart form, the query string will be created using the multipart form specifications.BRBR |
Additionally, you can specify whether each paramter should be URL encoded. If you are not sure what this means, it is probably best to select it. If your values contain characters such as & or spaces, or question marks, then encoding is usually required.
...
| No |
Filename | Name of the file to send. If left blank, JMeter does not send a file, if filled in, JMeter automatically sends the request as a multipart form request. | No |
Parameter Name | Name of the web request parameter. | No (Yes if Filename filled in) |
MIME Type | MIME type (for example, text/plain). | No (Yes if Filename filled in) |
Retrieve All Embedded Resources from HTML Files | Tell JMeter to parse the HTML file and send HTTP/HTTPS requests for all images, Java applets, JavaScript files, CSSs, etc. referenced in the file. | No |
Use as monitor | For use with the Monitor Results listener. | No |
See Also:
\[wiki:Self:UserManual/Elements#assertions Assertion\]unmigrated-wiki-markupWiki Markup - \[ :UserManual/BuildWebTest: Building a Web Test Plan\|UserManual BuildWebTest]
\Wiki Markup - [ :UserManual/BuildAdvancedWeb: Building an Advanced Web Test Plan\|UserManual BuildAdvancedWeb]
\[:../HttpAuthorizationManager: HTTP Authorization Manager\]Wiki Markup \[:../HttpCookieManagaer:Wiki Markup - HTTP Cookie Manager\]
\[:../HttpHeaderManager: HTTP Header Manager\]Wiki Markup Wiki Markup - \[:../HtmlLinkParser: HTML Link Parser\]unmigrated-wiki-markup\[:..
- /HttpProxyServier: HTTP Proxy Server\]unmigrated-wiki-markup
- \[:../HttpRequestDefaults: HTTP Request Defaults\]
\[wiki:Self:UserManual/BuildAdvancedWeb#urlrewriting HTTP Requests and Session ID's: URL Rewriting\]Wiki Markup