Many Web sites (especially those using J2EE application servers) use the JSESSIONID approach to managing sessions. This involves sending a cookie (JSESSIONID) during the login process, and the browser generating a URL request containing the string ';jsessionid=nnnnnnnn' in return. The cookie value and the URL value must match.
Cookies are sent dynamically, so to prevent future playbacks from generating URL requests with the wrong “;jsessionid=” string embedded, when the playback engine sees that a URL has the string “;jsessionid=” as part of the URL, it automatically replaces the value of the JSESSIONID parameter with the value sent in the JSESSIONID cookie. This ensures that URLs sent in CCL playback are consistent with the actual JSESSIONID value.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
