kernelkoder

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-02-22
05:31
387 views
correlation session id principle question
usually, what need to be correlated is session id from server
for example:
--------------- ------------- client browser web server --------------- -------------- 1. --------------------> web request1 2. <-------------------- session_id1 assigned from server 3. --------------------> web request2(with session_id1)
how did web server recognize the session_id1 in web request2? did it remember the last time's session id in server side?
1 Reply


Absent Member..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2013-02-22
23:56
Your question is not clear. You seem to have an issue with correlating a dynamic session ID which is returned by the web server but then you proceed to ask about what the web server does.
I cannot tell you how the web server behaves but you already stated in your example that the sessionId is returned from either a HTTP GET or POST (request1). You just need to use a web_reg_save_param function before request1 to capture the sessionId. When captured, this results in a parameter (ie. param1 or whatever you named it). Then in your Vugen script for request2, you substituted the static sessionId value with {param1}.
I cannot tell you how the web server behaves but you already stated in your example that the sessionId is returned from either a HTTP GET or POST (request1). You just need to use a web_reg_save_param function before request1 to capture the sessionId. When captured, this results in a parameter (ie. param1 or whatever you named it). Then in your Vugen script for request2, you substituted the static sessionId value with {param1}.