|
|
After recording a business case, if your Web application has URL Rewriting for session management, Web Performance Test Studio enables you to dynamically substitute the session data in the URL from an external source such as database or CSV file or from cookies or response body.
Handling Session Data in URL Rewrites
URL Rewriting is one of the popular session tracking method used for Non-cookie browsers to save session information. URL Rewriting tracks the user's session by including the session ID in the URL (to carry information from one HTML page to another). The information is stored inside the URL, as an additional parameter where all the links on a page are re-written so that the server side program receives the old as well as new data. Thus a session (or a connection is maintained between multiple pages) for every user.
The following table explains the four types of URL Rewrites supported by QEngine:
|
Type |
Description |
How to Configure |
|---|---|---|
|
Replace Complete URL |
||
|
Replace Complete URL |
URL will be completely
rewritten by the server to include session details. URL rewriting
involves finding all links that will be written back to the browser, and
rewriting them to include the session ID. For example, a link that looks
like this: |
If your recorded URL belongs to this category then choose the option Select Complete URL and substitute the values either from response body or from an element attribute. Refer to Configuring Replace Complete URL for the details. |
|
Session Data Embedded in URL |
||
|
Embedded in URL |
Session data embedded within a URL segment as name value pairs. For e.g.,
http://testserver:8080/login.do; jsessionid=AEGH12SEWF33RFFSF?view=network&id=10 |
If your recorded URL belongs to this category, parameters of this URL has to be selected and configured to fetch values either from database, CSV file, cookie, response body, element attribute, javascript or from URL. Play engine will extract the values by searching and parsing returned HTML content and embed it with the URL. Refer to the following link for the details. |
|
Session Data Embedded in Path |
||
|
Embedded in Path |
The session data is added as a new URL's path segment. Session data does not appear as name value pair.
http://testserver:8080/login.do/AEGH12SEWF33RFFSF? view=network&id=10
|
If your recorded URL belongs to this category, parameters of this URL has to be selected and configured to fetch value either from database, CSV file, cookie, response body, javascript or from URL. Play engine will extract the values by searching and parsing returned HTML content and embed it with the URL path. Refer to the following link for the details. |
Configuring Session Data in URL Rewrites
To know the details of Configuring Session Data using URL Rewrites, please refer to the context-sensitive help in the following link.
|
|