I'm now trying to use the cookie manager to do the management for me, ie, not set the cookie manually. Here's what's confusing me:
In the app run from a browser, firefox live headers shows that the splash page sets a cookie. The login passes the same cookie, Doing this with Jmeter, I have a test plan with these added to a thread group: 1) Cookie manager - no entries. 2) HTTP request --> Splash page 3) HTTP request --> Login 4) HTTP request --> Generic data request. 5) Results tree. So in the results tree, the splash page shows: Set-Cookie: JSESSIONID=0DCBD82A086499D0736DF893472FF00D; Path=/ However, the login page results tree shows a new cookie Set-Cookie: JSESSIONID=B896AFE21E538E11D219023ACC1EDA66; Path=/ Any idea how to get the same cookie from the splash page passed into all subsequent requests? Thanks! Robert On 3/13/07, sebb <[EMAIL PROTECTED]> wrote:
Manually added cookies will be sent if they qualify; same as for cookies sent by the server. However if you select "clear cookies each iteration" they will only be sent the first time through the main loop. Cookies can be seen in the Tree View Listener. On 13/03/07, robert lazarski <[EMAIL PROTECTED]> wrote: > Ahh, thanks. Is it true that manually added cookies should be sent to > the server? Any guess on why they don't seem to be sent by my config > as I tried to explain it ? > > Robert > > On 3/13/07, sebb <[EMAIL PROTECTED]> wrote: > > The Cookie Manager does not show the cookies; only manually added > > cookies appear on the screen. > > > > > > On 13/03/07, robert lazarski <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > > > I'm using JMeter again after a few years. I picked up my old test plan > > > and am running 2.2 . For the life of me I can't get cookies to be sent > > > to the server or get the cookies received from the login to be picked > > > up. I used to be able to do that fine. What I did: > > > > > > 1) Added a thread group, and to that added the following: > > > 2) Added a cookie manager. > > > 3) Added a results tree. > > > 4) Added an http request with all the right params to login, seems to > > > work as I can see a cookie returned and debugging on the server shows > > > all is ok. > > > > > > However, the cookie manager shows no cookies! So I disabled the first > > > thread group and added a second. Repeated steps on 1-4, only now the > > > http request assumes a login has performed and does a query for data. > > > Also, I added the JSESSIONID returned from the first thread groups > > > result tree manually to the cookie manager in the second thread group. > > > First thread group has threads set to 0, also tried disabling. Using > > > wireshark on linux, I can't see the manual cookie I set being sent! > > > The request of course has an error, server debug shows no http session > > > and the results tree shows a new cookie along with errors. > > > > > > I'm sure I'm doing something boneheaded, can a kind soul point the > > > error of my ways ;-) ? > > > > > > Thanks, > > > Robert > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
