Re: cookie manager not working
I guess my confusion arises because most of the text talks about restricting the scope of the cookies and the RFC only allows you to broaden the scope.In any case the workaround is more than sufficient for these cases regards deepak On Fri, Jun 3, 2011 at 1:05 PM, sebb wrote: > On 3 June 2011 20:36, Deepak Shetty wrote: > > even www.wordpress.com does the same thing and it seems to work fine in > FF > > > > *https://en.wordpress.com/wp-login.php* > > POST /wp-login.php HTTP/1.1 > > Set-Cookie: wordpress=VALUE; expires=Fri, 17-Jun-2011 19:32:09 GMT; * > > path=/wp-admin;* domain=.wordpress.com; httponly > > > > the browser is at url "/" , the post is to url */wp-login.php *- what is > the > > path to be compared with - the url the browser is at or the URL that is > > being posted to. ? > > AIUI, the cookie path is to be compared with the current request URI, > i.e. /wp-login.php > > > > > regards > > deepak > > > > > > On Fri, Jun 3, 2011 at 4:26 AM, sebb wrote: > > > >> On 3 June 2011 04:27, Deepak Shetty wrote: > >> > You are right , that is the problem . However im wondering what the > right > >> > behavior is > >> > If I request "/testjmeter/wp-login.php" > >> > Then arent these valid paths for set-cookie > >> > / > >> > /testjmeter > >> > /testjmeter/wp-login.php > >> > /testjmeter/child/ --> This is the problematic one. I was under the > >> > impression this was allowed? > >> > >> The Netscape specs (such as they are) are not entirely clear on this. > >> I have found the following: > >> > >> [1] the pathname component of the URL is compared with the path > >> attribute, and if there is a match, the cookie is considered valid and > >> is sent along with the URL request. The path "/foo" would match > >> "/foobar" and "/foo/bar.html". The path "/" is the most general path. > >> > >> RFC2109 says cookies should be rejected if "The value for the Path > >> attribute is not a prefix of the request-URI." > >> > >> My reading is that /testjmeter/child/ is not allowed by either cookie > >> spec. > >> > >> > if my page is at the root /wp-login.php then I think all directories > >> under / > >> > are allowed in the Set-Cookie? > >> > >> If the path is set to /, then all files and directories under it are > >> allowed. > >> However, as far as I can tell, if the path is set to /wp-login.php > >> then it is only valid for /wp-login.php (and ./wp-login.php/xzy if > >> that exists) > >> > >> > I tried to look through the cookie RFC and didnt seem to find > information > >> > one way or the other > >> > >> See above. > >> > >> > I can verify your fix works > >> > CookieManager.check.cookies=false -- Daniel this should work without > >> needing > >> > to manipulate cookies (In my example set this in jmeter.properties and > >> > disable the pre processor that adds the cookie) > >> > >> Best to add this to user.properties > >> > >> [1] http://curl.haxx.se/rfc/cookie_spec.html > >> [2] > >> > http://devedge-temp.mozilla.org/library/manuals/2000/javascript/1.3/reference/cookies.html > >> > >> - > >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >> > >> > > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
Re: cookie manager not working
On 3 June 2011 20:36, Deepak Shetty wrote: > even www.wordpress.com does the same thing and it seems to work fine in FF > > *https://en.wordpress.com/wp-login.php* > POST /wp-login.php HTTP/1.1 > Set-Cookie: wordpress=VALUE; expires=Fri, 17-Jun-2011 19:32:09 GMT; * > path=/wp-admin;* domain=.wordpress.com; httponly > > the browser is at url "/" , the post is to url */wp-login.php *- what is the > path to be compared with - the url the browser is at or the URL that is > being posted to. ? AIUI, the cookie path is to be compared with the current request URI, i.e. /wp-login.php > > regards > deepak > > > On Fri, Jun 3, 2011 at 4:26 AM, sebb wrote: > >> On 3 June 2011 04:27, Deepak Shetty wrote: >> > You are right , that is the problem . However im wondering what the right >> > behavior is >> > If I request "/testjmeter/wp-login.php" >> > Then arent these valid paths for set-cookie >> > / >> > /testjmeter >> > /testjmeter/wp-login.php >> > /testjmeter/child/ --> This is the problematic one. I was under the >> > impression this was allowed? >> >> The Netscape specs (such as they are) are not entirely clear on this. >> I have found the following: >> >> [1] the pathname component of the URL is compared with the path >> attribute, and if there is a match, the cookie is considered valid and >> is sent along with the URL request. The path "/foo" would match >> "/foobar" and "/foo/bar.html". The path "/" is the most general path. >> >> RFC2109 says cookies should be rejected if "The value for the Path >> attribute is not a prefix of the request-URI." >> >> My reading is that /testjmeter/child/ is not allowed by either cookie >> spec. >> >> > if my page is at the root /wp-login.php then I think all directories >> under / >> > are allowed in the Set-Cookie? >> >> If the path is set to /, then all files and directories under it are >> allowed. >> However, as far as I can tell, if the path is set to /wp-login.php >> then it is only valid for /wp-login.php (and ./wp-login.php/xzy if >> that exists) >> >> > I tried to look through the cookie RFC and didnt seem to find information >> > one way or the other >> >> See above. >> >> > I can verify your fix works >> > CookieManager.check.cookies=false -- Daniel this should work without >> needing >> > to manipulate cookies (In my example set this in jmeter.properties and >> > disable the pre processor that adds the cookie) >> >> Best to add this to user.properties >> >> [1] http://curl.haxx.se/rfc/cookie_spec.html >> [2] >> http://devedge-temp.mozilla.org/library/manuals/2000/javascript/1.3/reference/cookies.html >> >> - >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
even www.wordpress.com does the same thing and it seems to work fine in FF *https://en.wordpress.com/wp-login.php* POST /wp-login.php HTTP/1.1 Set-Cookie: wordpress=VALUE; expires=Fri, 17-Jun-2011 19:32:09 GMT; * path=/wp-admin;* domain=.wordpress.com; httponly the browser is at url "/" , the post is to url */wp-login.php *- what is the path to be compared with - the url the browser is at or the URL that is being posted to. ? regards deepak On Fri, Jun 3, 2011 at 4:26 AM, sebb wrote: > On 3 June 2011 04:27, Deepak Shetty wrote: > > You are right , that is the problem . However im wondering what the right > > behavior is > > If I request "/testjmeter/wp-login.php" > > Then arent these valid paths for set-cookie > > / > > /testjmeter > > /testjmeter/wp-login.php > > /testjmeter/child/ --> This is the problematic one. I was under the > > impression this was allowed? > > The Netscape specs (such as they are) are not entirely clear on this. > I have found the following: > > [1] the pathname component of the URL is compared with the path > attribute, and if there is a match, the cookie is considered valid and > is sent along with the URL request. The path "/foo" would match > "/foobar" and "/foo/bar.html". The path "/" is the most general path. > > RFC2109 says cookies should be rejected if "The value for the Path > attribute is not a prefix of the request-URI." > > My reading is that /testjmeter/child/ is not allowed by either cookie > spec. > > > if my page is at the root /wp-login.php then I think all directories > under / > > are allowed in the Set-Cookie? > > If the path is set to /, then all files and directories under it are > allowed. > However, as far as I can tell, if the path is set to /wp-login.php > then it is only valid for /wp-login.php (and ./wp-login.php/xzy if > that exists) > > > I tried to look through the cookie RFC and didnt seem to find information > > one way or the other > > See above. > > > I can verify your fix works > > CookieManager.check.cookies=false -- Daniel this should work without > needing > > to manipulate cookies (In my example set this in jmeter.properties and > > disable the pre processor that adds the cookie) > > Best to add this to user.properties > > [1] http://curl.haxx.se/rfc/cookie_spec.html > [2] > http://devedge-temp.mozilla.org/library/manuals/2000/javascript/1.3/reference/cookies.html > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
Re: cookie manager not working
On 3 June 2011 04:27, Deepak Shetty wrote: > You are right , that is the problem . However im wondering what the right > behavior is > If I request "/testjmeter/wp-login.php" > Then arent these valid paths for set-cookie > / > /testjmeter > /testjmeter/wp-login.php > /testjmeter/child/ --> This is the problematic one. I was under the > impression this was allowed? The Netscape specs (such as they are) are not entirely clear on this. I have found the following: [1] the pathname component of the URL is compared with the path attribute, and if there is a match, the cookie is considered valid and is sent along with the URL request. The path "/foo" would match "/foobar" and "/foo/bar.html". The path "/" is the most general path. RFC2109 says cookies should be rejected if "The value for the Path attribute is not a prefix of the request-URI." My reading is that /testjmeter/child/ is not allowed by either cookie spec. > if my page is at the root /wp-login.php then I think all directories under / > are allowed in the Set-Cookie? If the path is set to /, then all files and directories under it are allowed. However, as far as I can tell, if the path is set to /wp-login.php then it is only valid for /wp-login.php (and ./wp-login.php/xzy if that exists) > I tried to look through the cookie RFC and didnt seem to find information > one way or the other See above. > I can verify your fix works > CookieManager.check.cookies=false -- Daniel this should work without needing > to manipulate cookies (In my example set this in jmeter.properties and > disable the pre processor that adds the cookie) Best to add this to user.properties [1] http://curl.haxx.se/rfc/cookie_spec.html [2] http://devedge-temp.mozilla.org/library/manuals/2000/javascript/1.3/reference/cookies.html - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
On 3 June 2011 05:01, Daniel Watrous wrote: > Thank You. > > This works wonderfully. It's exactly what I was hoping to be able to > accomplish. You all really went the extra mile to help me out. > > Can anyone tell me why my exclude definitions on the proxy didn't > exclude the files I expected? I already answered that. Probably spurious characters in the regexes. BTW, you can select the Workbench and save it to a file, then Merge it later. > Daniel > > On Thu, Jun 2, 2011 at 9:27 PM, Deepak Shetty wrote: >> You are right , that is the problem . However im wondering what the right >> behavior is >> If I request "/testjmeter/wp-login.php" >> Then arent these valid paths for set-cookie >> / >> /testjmeter >> /testjmeter/wp-login.php >> /testjmeter/child/ --> This is the problematic one. I was under the >> impression this was allowed? >> >> if my page is at the root /wp-login.php then I think all directories under / >> are allowed in the Set-Cookie? >> >> I tried to look through the cookie RFC and didnt seem to find information >> one way or the other >> >> I can verify your fix works >> CookieManager.check.cookies=false -- Daniel this should work without needing >> to manipulate cookies (In my example set this in jmeter.properties and >> disable the pre processor that adds the cookie) >> >> >> >> regards >> deepak >> >> >> >> >> >> >> On Thu, Jun 2, 2011 at 6:48 PM, sebb wrote: >> >>> On 3 June 2011 02:32, Deepak Shetty wrote: >>> > Ok i will . Visually the cookies look fine and one of them does get sent >>> in >>> > the next request (the one without path and http only) >>> >>> When I try, I get several cookies rejected, e.g. with the message: >>> >>> (Illegal path attribute "/testjmeter/wp-admin". Path of origin: >>> "/testjmeter/wp-login.php") >>> >>> Maybe that is part of the problem? >>> >>> > Daniel : see if >>> > >>> http://cid-1bd02fe33f80b8ac.office.live.com/self.aspx/Public/jmeter/wordpress.jmxworks >>> > for you. I added the missing cookie programattically (various >>> > hardcodes but you shoould be able to login - logout doesnt work because I >>> > need to remove the cookie i set) >>> > >>> > regards >>> > deepak >>> > >>> > On Thu, Jun 2, 2011 at 6:18 PM, sebb wrote: >>> > >>> >> On 3 June 2011 02:10, Deepak Shetty wrote: >>> >> > There seems to be a Jmeter Bug >>> >> > >>> >> > Login request gets the following as response >>> >> > >>> >> > Set-Cookie: wordpress_test_cookie=WP+Cookie+check; path=/testjmeter/ >>> >> > Set-Cookie: >>> >> > >>> >> >>> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; >>> >> > path=/testjmeter/wp-content/plugins; httponly >>> >> > *Set-Cookie: >>> >> > >>> >> >>> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; >>> >> > path=/testjmeter/wp-admin; httponly >>> >> > *Set-Cookie: >>> >> > >>> >> >>> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1; >>> >> > >>> >> > All good here >>> >> >>> >> Perhaps not - please enable Cookie Manager Debug logging to see if any >>> >> of the cookies have been rejected, and why. >>> >> >>> >> > The next request >>> >> > GET http://authnet.danielwatrous.com/testjmeter/wp-admin/ >>> >> > Cookie Data: >>> >> > wordpress_test_cookie=WP+Cookie+check; >>> >> > >>> >> >>> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1 >>> >> > >>> >> > doesnt have the cookie above that I bolded which has an explicit path >>> >> and >>> >> > httponly (not sure which of the attributes cause a problem) >>> >> > >>> >> > Programatically setting the cookies seem to be the only workaround >>> >> without >>> >> > code fix, can you please confirm (I dont think expiry
Re: cookie manager not working
>Can anyone tell me why my exclude definitions on the proxy didn't >exclude the files I expected? Sorry I dont see where this question is? Its probably best to start a new thread. On Thu, Jun 2, 2011 at 9:01 PM, Daniel Watrous wrote: > Thank You. > > This works wonderfully. It's exactly what I was hoping to be able to > accomplish. You all really went the extra mile to help me out. > > Can anyone tell me why my exclude definitions on the proxy didn't > exclude the files I expected? > > Daniel > > On Thu, Jun 2, 2011 at 9:27 PM, Deepak Shetty wrote: > > You are right , that is the problem . However im wondering what the right > > behavior is > > If I request "/testjmeter/wp-login.php" > > Then arent these valid paths for set-cookie > > / > > /testjmeter > > /testjmeter/wp-login.php > > /testjmeter/child/ --> This is the problematic one. I was under the > > impression this was allowed? > > > > if my page is at the root /wp-login.php then I think all directories > under / > > are allowed in the Set-Cookie? > > > > I tried to look through the cookie RFC and didnt seem to find information > > one way or the other > > > > I can verify your fix works > > CookieManager.check.cookies=false -- Daniel this should work without > needing > > to manipulate cookies (In my example set this in jmeter.properties and > > disable the pre processor that adds the cookie) > > > > > > > > regards > > deepak > > > > > > > > > > > > > > On Thu, Jun 2, 2011 at 6:48 PM, sebb wrote: > > > >> On 3 June 2011 02:32, Deepak Shetty wrote: > >> > Ok i will . Visually the cookies look fine and one of them does get > sent > >> in > >> > the next request (the one without path and http only) > >> > >> When I try, I get several cookies rejected, e.g. with the message: > >> > >> (Illegal path attribute "/testjmeter/wp-admin". Path of origin: > >> "/testjmeter/wp-login.php") > >> > >> Maybe that is part of the problem? > >> > >> > Daniel : see if > >> > > >> > http://cid-1bd02fe33f80b8ac.office.live.com/self.aspx/Public/jmeter/wordpress.jmxworks > >> > for you. I added the missing cookie programattically (various > >> > hardcodes but you shoould be able to login - logout doesnt work > because I > >> > need to remove the cookie i set) > >> > > >> > regards > >> > deepak > >> > > >> > On Thu, Jun 2, 2011 at 6:18 PM, sebb wrote: > >> > > >> >> On 3 June 2011 02:10, Deepak Shetty wrote: > >> >> > There seems to be a Jmeter Bug > >> >> > > >> >> > Login request gets the following as response > >> >> > > >> >> > Set-Cookie: wordpress_test_cookie=WP+Cookie+check; > path=/testjmeter/ > >> >> > Set-Cookie: > >> >> > > >> >> > >> > wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; > >> >> > path=/testjmeter/wp-content/plugins; httponly > >> >> > *Set-Cookie: > >> >> > > >> >> > >> > wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; > >> >> > path=/testjmeter/wp-admin; httponly > >> >> > *Set-Cookie: > >> >> > > >> >> > >> > wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1; > >> >> > > >> >> > All good here > >> >> > >> >> Perhaps not - please enable Cookie Manager Debug logging to see if > any > >> >> of the cookies have been rejected, and why. > >> >> > >> >> > The next request > >> >> > GET http://authnet.danielwatrous.com/testjmeter/wp-admin/ > >> >> > Cookie Data: > >> >> > wordpress_test_cookie=WP+Cookie+check; > >> >> > > >> >> > >> > wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1 > >> >> > > >> >> > doesnt have the cookie above that I bolded which has an explicit > path > >> >> and > >> >> > httponly (not sure which of the attributes cause a problem) > >> >>
Re: cookie manager not working
Thank You. This works wonderfully. It's exactly what I was hoping to be able to accomplish. You all really went the extra mile to help me out. Can anyone tell me why my exclude definitions on the proxy didn't exclude the files I expected? Daniel On Thu, Jun 2, 2011 at 9:27 PM, Deepak Shetty wrote: > You are right , that is the problem . However im wondering what the right > behavior is > If I request "/testjmeter/wp-login.php" > Then arent these valid paths for set-cookie > / > /testjmeter > /testjmeter/wp-login.php > /testjmeter/child/ --> This is the problematic one. I was under the > impression this was allowed? > > if my page is at the root /wp-login.php then I think all directories under / > are allowed in the Set-Cookie? > > I tried to look through the cookie RFC and didnt seem to find information > one way or the other > > I can verify your fix works > CookieManager.check.cookies=false -- Daniel this should work without needing > to manipulate cookies (In my example set this in jmeter.properties and > disable the pre processor that adds the cookie) > > > > regards > deepak > > > > > > > On Thu, Jun 2, 2011 at 6:48 PM, sebb wrote: > >> On 3 June 2011 02:32, Deepak Shetty wrote: >> > Ok i will . Visually the cookies look fine and one of them does get sent >> in >> > the next request (the one without path and http only) >> >> When I try, I get several cookies rejected, e.g. with the message: >> >> (Illegal path attribute "/testjmeter/wp-admin". Path of origin: >> "/testjmeter/wp-login.php") >> >> Maybe that is part of the problem? >> >> > Daniel : see if >> > >> http://cid-1bd02fe33f80b8ac.office.live.com/self.aspx/Public/jmeter/wordpress.jmxworks >> > for you. I added the missing cookie programattically (various >> > hardcodes but you shoould be able to login - logout doesnt work because I >> > need to remove the cookie i set) >> > >> > regards >> > deepak >> > >> > On Thu, Jun 2, 2011 at 6:18 PM, sebb wrote: >> > >> >> On 3 June 2011 02:10, Deepak Shetty wrote: >> >> > There seems to be a Jmeter Bug >> >> > >> >> > Login request gets the following as response >> >> > >> >> > Set-Cookie: wordpress_test_cookie=WP+Cookie+check; path=/testjmeter/ >> >> > Set-Cookie: >> >> > >> >> >> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; >> >> > path=/testjmeter/wp-content/plugins; httponly >> >> > *Set-Cookie: >> >> > >> >> >> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; >> >> > path=/testjmeter/wp-admin; httponly >> >> > *Set-Cookie: >> >> > >> >> >> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1; >> >> > >> >> > All good here >> >> >> >> Perhaps not - please enable Cookie Manager Debug logging to see if any >> >> of the cookies have been rejected, and why. >> >> >> >> > The next request >> >> > GET http://authnet.danielwatrous.com/testjmeter/wp-admin/ >> >> > Cookie Data: >> >> > wordpress_test_cookie=WP+Cookie+check; >> >> > >> >> >> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1 >> >> > >> >> > doesnt have the cookie above that I bolded which has an explicit path >> >> and >> >> > httponly (not sure which of the attributes cause a problem) >> >> > >> >> > Programatically setting the cookies seem to be the only workaround >> >> without >> >> > code fix, can you please confirm (I dont think expiry date has >> naything >> >> to >> >> > do with , like you say , past expiry is used to delete a cookie) >> >> > regards >> >> > deepak >> >> > >> >> > >> >> > On Thu, Jun 2, 2011 at 5:52 PM, sebb wrote: >> >> > >> >> >> Yes; perhaps it is deliberately sending expired dates in order to >> >> >> delete the cookies. I have seen another server do this. >> >> >> >> >> >> From some biref experiments with your test site, I suspect the logi
Re: cookie manager not working
You are right , that is the problem . However im wondering what the right behavior is If I request "/testjmeter/wp-login.php" Then arent these valid paths for set-cookie / /testjmeter /testjmeter/wp-login.php /testjmeter/child/ --> This is the problematic one. I was under the impression this was allowed? if my page is at the root /wp-login.php then I think all directories under / are allowed in the Set-Cookie? I tried to look through the cookie RFC and didnt seem to find information one way or the other I can verify your fix works CookieManager.check.cookies=false -- Daniel this should work without needing to manipulate cookies (In my example set this in jmeter.properties and disable the pre processor that adds the cookie) regards deepak On Thu, Jun 2, 2011 at 6:48 PM, sebb wrote: > On 3 June 2011 02:32, Deepak Shetty wrote: > > Ok i will . Visually the cookies look fine and one of them does get sent > in > > the next request (the one without path and http only) > > When I try, I get several cookies rejected, e.g. with the message: > > (Illegal path attribute "/testjmeter/wp-admin". Path of origin: > "/testjmeter/wp-login.php") > > Maybe that is part of the problem? > > > Daniel : see if > > > http://cid-1bd02fe33f80b8ac.office.live.com/self.aspx/Public/jmeter/wordpress.jmxworks > > for you. I added the missing cookie programattically (various > > hardcodes but you shoould be able to login - logout doesnt work because I > > need to remove the cookie i set) > > > > regards > > deepak > > > > On Thu, Jun 2, 2011 at 6:18 PM, sebb wrote: > > > >> On 3 June 2011 02:10, Deepak Shetty wrote: > >> > There seems to be a Jmeter Bug > >> > > >> > Login request gets the following as response > >> > > >> > Set-Cookie: wordpress_test_cookie=WP+Cookie+check; path=/testjmeter/ > >> > Set-Cookie: > >> > > >> > wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; > >> > path=/testjmeter/wp-content/plugins; httponly > >> > *Set-Cookie: > >> > > >> > wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; > >> > path=/testjmeter/wp-admin; httponly > >> > *Set-Cookie: > >> > > >> > wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1; > >> > > >> > All good here > >> > >> Perhaps not - please enable Cookie Manager Debug logging to see if any > >> of the cookies have been rejected, and why. > >> > >> > The next request > >> > GET http://authnet.danielwatrous.com/testjmeter/wp-admin/ > >> > Cookie Data: > >> > wordpress_test_cookie=WP+Cookie+check; > >> > > >> > wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1 > >> > > >> > doesnt have the cookie above that I bolded which has an explicit path > >> and > >> > httponly (not sure which of the attributes cause a problem) > >> > > >> > Programatically setting the cookies seem to be the only workaround > >> without > >> > code fix, can you please confirm (I dont think expiry date has > naything > >> to > >> > do with , like you say , past expiry is used to delete a cookie) > >> > regards > >> > deepak > >> > > >> > > >> > On Thu, Jun 2, 2011 at 5:52 PM, sebb wrote: > >> > > >> >> Yes; perhaps it is deliberately sending expired dates in order to > >> >> delete the cookies. I have seen another server do this. > >> >> > >> >> From some biref experiments with your test site, I suspect the login > >> >> problem is nothing to do with expired cookies after all, but there is > >> >> probably some other setting that is not correct. > >> >> > >> >> Look for parameters that have odd-looking values; they may be being > >> >> set by Javascript in the browser, in which case you will have to work > >> >> out how to extract the relevant values from the previous reponse. > >> >> > >> >> Or record the login twice, and compare the generated test plans to > see > >> >> which entries have changed. You then have to work out how to extract > >> >> the values they need. The Save Responses to a File Listener can be > >> &g
Re: cookie manager not working
On 3 June 2011 02:48, sebb wrote: > On 3 June 2011 02:32, Deepak Shetty wrote: >> Ok i will . Visually the cookies look fine and one of them does get sent in >> the next request (the one without path and http only) > > When I try, I get several cookies rejected, e.g. with the message: > > (Illegal path attribute "/testjmeter/wp-admin". Path of origin: > "/testjmeter/wp-login.php") > > Maybe that is part of the problem? I'd forgotten - there is a JMeter property one can set to avoid checking cookies for validity: CookieManager.check.cookies=false Setting that prevents the invalid cookie paths from being rejected. >> Daniel : see if >> http://cid-1bd02fe33f80b8ac.office.live.com/self.aspx/Public/jmeter/wordpress.jmxworks >> for you. I added the missing cookie programattically (various >> hardcodes but you shoould be able to login - logout doesnt work because I >> need to remove the cookie i set) >> >> regards >> deepak >> >> On Thu, Jun 2, 2011 at 6:18 PM, sebb wrote: >> >>> On 3 June 2011 02:10, Deepak Shetty wrote: >>> > There seems to be a Jmeter Bug >>> > >>> > Login request gets the following as response >>> > >>> > Set-Cookie: wordpress_test_cookie=WP+Cookie+check; path=/testjmeter/ >>> > Set-Cookie: >>> > >>> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; >>> > path=/testjmeter/wp-content/plugins; httponly >>> > *Set-Cookie: >>> > >>> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; >>> > path=/testjmeter/wp-admin; httponly >>> > *Set-Cookie: >>> > >>> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1; >>> > >>> > All good here >>> >>> Perhaps not - please enable Cookie Manager Debug logging to see if any >>> of the cookies have been rejected, and why. >>> >>> > The next request >>> > GET http://authnet.danielwatrous.com/testjmeter/wp-admin/ >>> > Cookie Data: >>> > wordpress_test_cookie=WP+Cookie+check; >>> > >>> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1 >>> > >>> > doesnt have the cookie above that I bolded which has an explicit path >>> and >>> > httponly (not sure which of the attributes cause a problem) >>> > >>> > Programatically setting the cookies seem to be the only workaround >>> without >>> > code fix, can you please confirm (I dont think expiry date has naything >>> to >>> > do with , like you say , past expiry is used to delete a cookie) >>> > regards >>> > deepak >>> > >>> > >>> > On Thu, Jun 2, 2011 at 5:52 PM, sebb wrote: >>> > >>> >> Yes; perhaps it is deliberately sending expired dates in order to >>> >> delete the cookies. I have seen another server do this. >>> >> >>> >> From some biref experiments with your test site, I suspect the login >>> >> problem is nothing to do with expired cookies after all, but there is >>> >> probably some other setting that is not correct. >>> >> >>> >> Look for parameters that have odd-looking values; they may be being >>> >> set by Javascript in the browser, in which case you will have to work >>> >> out how to extract the relevant values from the previous reponse. >>> >> >>> >> Or record the login twice, and compare the generated test plans to see >>> >> which entries have changed. You then have to work out how to extract >>> >> the values they need. The Save Responses to a File Listener can be >>> >> helpful here. >>> >> >>> >> BTW, JMeter cannot currently handle deflate encoding, so make sure you >>> >> don't enable that in the Header Manager. >>> >> >>> >> Also, Excludes *do* work - make sure that there aren't any trailing >>> >> spaces or other spurious characters in the fields. >>> >> >>> >> On 3 June 2011 01:30, Daniel Watrous wrote: >>> >> > Did any of you notice that the Date of the request is accurate and so >>> >> > are some of the cookies? WordPress seems to deliberately send the >>&
Re: cookie manager not working
On 3 June 2011 02:32, Deepak Shetty wrote: > Ok i will . Visually the cookies look fine and one of them does get sent in > the next request (the one without path and http only) When I try, I get several cookies rejected, e.g. with the message: (Illegal path attribute "/testjmeter/wp-admin". Path of origin: "/testjmeter/wp-login.php") Maybe that is part of the problem? > Daniel : see if > http://cid-1bd02fe33f80b8ac.office.live.com/self.aspx/Public/jmeter/wordpress.jmxworks > for you. I added the missing cookie programattically (various > hardcodes but you shoould be able to login - logout doesnt work because I > need to remove the cookie i set) > > regards > deepak > > On Thu, Jun 2, 2011 at 6:18 PM, sebb wrote: > >> On 3 June 2011 02:10, Deepak Shetty wrote: >> > There seems to be a Jmeter Bug >> > >> > Login request gets the following as response >> > >> > Set-Cookie: wordpress_test_cookie=WP+Cookie+check; path=/testjmeter/ >> > Set-Cookie: >> > >> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; >> > path=/testjmeter/wp-content/plugins; httponly >> > *Set-Cookie: >> > >> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; >> > path=/testjmeter/wp-admin; httponly >> > *Set-Cookie: >> > >> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1; >> > >> > All good here >> >> Perhaps not - please enable Cookie Manager Debug logging to see if any >> of the cookies have been rejected, and why. >> >> > The next request >> > GET http://authnet.danielwatrous.com/testjmeter/wp-admin/ >> > Cookie Data: >> > wordpress_test_cookie=WP+Cookie+check; >> > >> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1 >> > >> > doesnt have the cookie above that I bolded which has an explicit path >> and >> > httponly (not sure which of the attributes cause a problem) >> > >> > Programatically setting the cookies seem to be the only workaround >> without >> > code fix, can you please confirm (I dont think expiry date has naything >> to >> > do with , like you say , past expiry is used to delete a cookie) >> > regards >> > deepak >> > >> > >> > On Thu, Jun 2, 2011 at 5:52 PM, sebb wrote: >> > >> >> Yes; perhaps it is deliberately sending expired dates in order to >> >> delete the cookies. I have seen another server do this. >> >> >> >> From some biref experiments with your test site, I suspect the login >> >> problem is nothing to do with expired cookies after all, but there is >> >> probably some other setting that is not correct. >> >> >> >> Look for parameters that have odd-looking values; they may be being >> >> set by Javascript in the browser, in which case you will have to work >> >> out how to extract the relevant values from the previous reponse. >> >> >> >> Or record the login twice, and compare the generated test plans to see >> >> which entries have changed. You then have to work out how to extract >> >> the values they need. The Save Responses to a File Listener can be >> >> helpful here. >> >> >> >> BTW, JMeter cannot currently handle deflate encoding, so make sure you >> >> don't enable that in the Header Manager. >> >> >> >> Also, Excludes *do* work - make sure that there aren't any trailing >> >> spaces or other spurious characters in the fields. >> >> >> >> On 3 June 2011 01:30, Daniel Watrous wrote: >> >> > Did any of you notice that the Date of the request is accurate and so >> >> > are some of the cookies? WordPress seems to deliberately send the >> >> > login related cookies with the year old expiration. Others are fine. >> >> > >> >> > I mention this because there seems to be an idea that the server time >> >> > is configured wrong. >> >> > >> >> > On Thu, Jun 2, 2011 at 4:32 PM, sebb wrote: >> >> >> On 2 June 2011 17:26, Bruce Ide wrote: >> >> >>> > I think it's a bit premature to suggest that WordPress is broken. >> It >> >> >>> > is used on tens of millions of sites
Re: cookie manager not working
Ok i will . Visually the cookies look fine and one of them does get sent in the next request (the one without path and http only) Daniel : see if http://cid-1bd02fe33f80b8ac.office.live.com/self.aspx/Public/jmeter/wordpress.jmxworks for you. I added the missing cookie programattically (various hardcodes but you shoould be able to login - logout doesnt work because I need to remove the cookie i set) regards deepak On Thu, Jun 2, 2011 at 6:18 PM, sebb wrote: > On 3 June 2011 02:10, Deepak Shetty wrote: > > There seems to be a Jmeter Bug > > > > Login request gets the following as response > > > > Set-Cookie: wordpress_test_cookie=WP+Cookie+check; path=/testjmeter/ > > Set-Cookie: > > > wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; > > path=/testjmeter/wp-content/plugins; httponly > > *Set-Cookie: > > > wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1; > > path=/testjmeter/wp-admin; httponly > > *Set-Cookie: > > > wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1; > > > > All good here > > Perhaps not - please enable Cookie Manager Debug logging to see if any > of the cookies have been rejected, and why. > > > The next request > > GET http://authnet.danielwatrous.com/testjmeter/wp-admin/ > > Cookie Data: > > wordpress_test_cookie=WP+Cookie+check; > > > wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1 > > > > doesnt have the cookie above that I bolded which has an explicit path > and > > httponly (not sure which of the attributes cause a problem) > > > > Programatically setting the cookies seem to be the only workaround > without > > code fix, can you please confirm (I dont think expiry date has naything > to > > do with , like you say , past expiry is used to delete a cookie) > > regards > > deepak > > > > > > On Thu, Jun 2, 2011 at 5:52 PM, sebb wrote: > > > >> Yes; perhaps it is deliberately sending expired dates in order to > >> delete the cookies. I have seen another server do this. > >> > >> From some biref experiments with your test site, I suspect the login > >> problem is nothing to do with expired cookies after all, but there is > >> probably some other setting that is not correct. > >> > >> Look for parameters that have odd-looking values; they may be being > >> set by Javascript in the browser, in which case you will have to work > >> out how to extract the relevant values from the previous reponse. > >> > >> Or record the login twice, and compare the generated test plans to see > >> which entries have changed. You then have to work out how to extract > >> the values they need. The Save Responses to a File Listener can be > >> helpful here. > >> > >> BTW, JMeter cannot currently handle deflate encoding, so make sure you > >> don't enable that in the Header Manager. > >> > >> Also, Excludes *do* work - make sure that there aren't any trailing > >> spaces or other spurious characters in the fields. > >> > >> On 3 June 2011 01:30, Daniel Watrous wrote: > >> > Did any of you notice that the Date of the request is accurate and so > >> > are some of the cookies? WordPress seems to deliberately send the > >> > login related cookies with the year old expiration. Others are fine. > >> > > >> > I mention this because there seems to be an idea that the server time > >> > is configured wrong. > >> > > >> > On Thu, Jun 2, 2011 at 4:32 PM, sebb wrote: > >> >> On 2 June 2011 17:26, Bruce Ide wrote: > >> >>> > I think it's a bit premature to suggest that WordPress is broken. > It > >> >>> > is used on tens of millions of sites and people are able to login > >> fine > >> >>> >every day. > >> >>> > >> >>> Number of users is not a quality metric! Look at Windows... (Heh heh > >> heh) > >> >>> > >> >>>> Well there's your problem! > >> >>>> > >> >>>> That only affects the cookies that are stored in the cookies file > >> >>>> (which is not normally used). > >> >>>> > >> >>>> > >> >>> Doh! It seemed like such a likely culprit, too! > >> >>&g
Re: cookie manager not working
On 3 June 2011 02:10, Deepak Shetty wrote:
> There seems to be a Jmeter Bug
>
> Login request gets the following as response
>
> Set-Cookie: wordpress_test_cookie=WP+Cookie+check; path=/testjmeter/
> Set-Cookie:
> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1;
> path=/testjmeter/wp-content/plugins; httponly
> *Set-Cookie:
> wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7Ca053ec10f70ffb4681edbea2e9c65bf1;
> path=/testjmeter/wp-admin; httponly
> *Set-Cookie:
> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1;
>
> All good here
Perhaps not - please enable Cookie Manager Debug logging to see if any
of the cookies have been rejected, and why.
> The next request
> GET http://authnet.danielwatrous.com/testjmeter/wp-admin/
> Cookie Data:
> wordpress_test_cookie=WP+Cookie+check;
> wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307235979%7C33bd157a96bcaf545769fa5d4b8483e1
>
> doesnt have the cookie above that I bolded which has an explicit path and
> httponly (not sure which of the attributes cause a problem)
>
> Programatically setting the cookies seem to be the only workaround without
> code fix, can you please confirm (I dont think expiry date has naything to
> do with , like you say , past expiry is used to delete a cookie)
> regards
> deepak
>
>
> On Thu, Jun 2, 2011 at 5:52 PM, sebb wrote:
>
>> Yes; perhaps it is deliberately sending expired dates in order to
>> delete the cookies. I have seen another server do this.
>>
>> From some biref experiments with your test site, I suspect the login
>> problem is nothing to do with expired cookies after all, but there is
>> probably some other setting that is not correct.
>>
>> Look for parameters that have odd-looking values; they may be being
>> set by Javascript in the browser, in which case you will have to work
>> out how to extract the relevant values from the previous reponse.
>>
>> Or record the login twice, and compare the generated test plans to see
>> which entries have changed. You then have to work out how to extract
>> the values they need. The Save Responses to a File Listener can be
>> helpful here.
>>
>> BTW, JMeter cannot currently handle deflate encoding, so make sure you
>> don't enable that in the Header Manager.
>>
>> Also, Excludes *do* work - make sure that there aren't any trailing
>> spaces or other spurious characters in the fields.
>>
>> On 3 June 2011 01:30, Daniel Watrous wrote:
>> > Did any of you notice that the Date of the request is accurate and so
>> > are some of the cookies? WordPress seems to deliberately send the
>> > login related cookies with the year old expiration. Others are fine.
>> >
>> > I mention this because there seems to be an idea that the server time
>> > is configured wrong.
>> >
>> > On Thu, Jun 2, 2011 at 4:32 PM, sebb wrote:
>> >> On 2 June 2011 17:26, Bruce Ide wrote:
>> >>> > I think it's a bit premature to suggest that WordPress is broken. It
>> >>> > is used on tens of millions of sites and people are able to login
>> fine
>> >>> >every day.
>> >>>
>> >>> Number of users is not a quality metric! Look at Windows... (Heh heh
>> heh)
>> >>>
>> >>>> Well there's your problem!
>> >>>>
>> >>>> That only affects the cookies that are stored in the cookies file
>> >>>> (which is not normally used).
>> >>>>
>> >>>>
>> >>> Doh! It seemed like such a likely culprit, too!
>> >>>
>> >>
>> >> The actual expiry code is similar:
>> >>
>> >> // Store session cookies as well as unexpired ones
>> >> if (exp == 0 || exp >= System.currentTimeMillis()) {
>> >> newCookie.setVersion(cookie.getVersion());
>> >> add(newCookie); // Has its own debug log; removes
>> >> matching cookies
>> >> } else {
>> >> removeMatchingCookies(newCookie);
>> >> if (debugEnabled){
>> >> log.debug("Dropping expired Cookie:
>> >> "+newCookie.toString());
>> >> }
>> >> }
>> >>
>> >>
>> >>>
>> >>>> &g
Re: cookie manager not working
time this has been reported [, and might > >>>> cause indigestion (!) in some cases]. > >>>> > >>>> > >>> Well it sounds like the web browser is also storing and using the > expired > >>> cookie, and the remote server is honoring it! That's like 3 different > bugs > >>> he's uncovered so far! At this point I'd be rampaging like... something > that > >>> rampages a LOT... through 2 or 3 different bug forums. > >>> > >>> I'm sure the Firefox guys would say "No it's not!" At least some people > in > >>> the "real world" do check cookie expiry dates, but it's probably > "optional". > >>> I'm not inclined to go digging through RFCs to find out. > >>> > >>> I'd say Wordpress sending out cookies from last year means someone > hasn't > >>> been minding a server like they should be. That really IS a problem. > >> > >> Agreed. > >> > >>> I suppose you could add a "Remove expiration dates" to the cookie > manager > >>> panel, or a "send expired cookies" checkbox to the httpclient. Probably > >>> wouldn't be a huge amount of coding, and would probably be only vaguely > >>> atrocious. > >> > >> It's fairly simple to change the code itself, but there is additional > >> work needed to implement the GUI change and update the documentation. > >> > >> It's not yet clear if this is a general problem affecting multiple > >> servers, or just WordPress servers, or just an issue with the > >> particular WordPress host. > >> > >>> Or perhaps a sampler or postprocessor that allows you to manipulate > explicit > >>> cookie values? That'd be a bit more work, but might be more palatable. > >> > >> That can be done already with the Regex Processor and Header Manager, > >> or using the BSH or BSF test elements. > >> > >> Might just be simpler to change the time on the box running JMeter ... > >> > >> - > >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >> > >> > > > > - > > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > > > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
Re: cookie manager not working
Yes; perhaps it is deliberately sending expired dates in order to
delete the cookies. I have seen another server do this.
>From some biref experiments with your test site, I suspect the login
problem is nothing to do with expired cookies after all, but there is
probably some other setting that is not correct.
Look for parameters that have odd-looking values; they may be being
set by Javascript in the browser, in which case you will have to work
out how to extract the relevant values from the previous reponse.
Or record the login twice, and compare the generated test plans to see
which entries have changed. You then have to work out how to extract
the values they need. The Save Responses to a File Listener can be
helpful here.
BTW, JMeter cannot currently handle deflate encoding, so make sure you
don't enable that in the Header Manager.
Also, Excludes *do* work - make sure that there aren't any trailing
spaces or other spurious characters in the fields.
On 3 June 2011 01:30, Daniel Watrous wrote:
> Did any of you notice that the Date of the request is accurate and so
> are some of the cookies? WordPress seems to deliberately send the
> login related cookies with the year old expiration. Others are fine.
>
> I mention this because there seems to be an idea that the server time
> is configured wrong.
>
> On Thu, Jun 2, 2011 at 4:32 PM, sebb wrote:
>> On 2 June 2011 17:26, Bruce Ide wrote:
>>> > I think it's a bit premature to suggest that WordPress is broken. It
>>> > is used on tens of millions of sites and people are able to login fine
>>> >every day.
>>>
>>> Number of users is not a quality metric! Look at Windows... (Heh heh heh)
>>>
>>>> Well there's your problem!
>>>>
>>>> That only affects the cookies that are stored in the cookies file
>>>> (which is not normally used).
>>>>
>>>>
>>> Doh! It seemed like such a likely culprit, too!
>>>
>>
>> The actual expiry code is similar:
>>
>> // Store session cookies as well as unexpired ones
>> if (exp == 0 || exp >= System.currentTimeMillis()) {
>> newCookie.setVersion(cookie.getVersion());
>> add(newCookie); // Has its own debug log; removes
>> matching cookies
>> } else {
>> removeMatchingCookies(newCookie);
>> if (debugEnabled){
>> log.debug("Dropping expired Cookie:
>> "+newCookie.toString());
>> }
>> }
>>
>>
>>>
>>>> > I'd be really hesitant to change the behavior of the test environment to
>>>> > mask a bug you uncovered, though. Sending expired cookies IS a bug, and
>>>> it's
>>>> > something the guys running the server should fix.
>>>>
>>>> If this is a general problem, I suppose it might make sense to add an
>>>> option to remove the expiry date from stale cookies, turning them into
>>>> session cookies.
>>>> But AFAIK this is the first time this has been reported [, and might
>>>> cause indigestion (!) in some cases].
>>>>
>>>>
>>> Well it sounds like the web browser is also storing and using the expired
>>> cookie, and the remote server is honoring it! That's like 3 different bugs
>>> he's uncovered so far! At this point I'd be rampaging like... something that
>>> rampages a LOT... through 2 or 3 different bug forums.
>>>
>>> I'm sure the Firefox guys would say "No it's not!" At least some people in
>>> the "real world" do check cookie expiry dates, but it's probably "optional".
>>> I'm not inclined to go digging through RFCs to find out.
>>>
>>> I'd say Wordpress sending out cookies from last year means someone hasn't
>>> been minding a server like they should be. That really IS a problem.
>>
>> Agreed.
>>
>>> I suppose you could add a "Remove expiration dates" to the cookie manager
>>> panel, or a "send expired cookies" checkbox to the httpclient. Probably
>>> wouldn't be a huge amount of coding, and would probably be only vaguely
>>> atrocious.
>>
>> It's fairly simple to change the code itself, but there is additional
>> work needed to implement the GUI change and update the documentation.
>>
>> It's not yet clear if this is a general problem affecting multiple
>>
Re: cookie manager not working
Hi
where are you seeing the invalid cookies(sorry havent seen your screencast).
i tried with firefox to login
I get
*http://authnet.danielwatrous.com/testjmeter/wp-login.php*
Set-Cookie: wordpress_test_cookie=WP+Cookie+check; path=/testjmeter/
Set-Cookie:
wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307234422%7Cc8c4e5bb5f9bacc38cf0d3f6a5a19125;
path=/testjmeter/wp-content/plugins; httponly
Set-Cookie:
wordpress_44389825f27c6e6c84e4f25396df08b1=admin%7C1307234422%7Cc8c4e5bb5f9bacc38cf0d3f6a5a19125;
path=/testjmeter/wp-admin; httponly
Set-Cookie:
wordpress_logged_in_44389825f27c6e6c84e4f25396df08b1=admin%7C1307234422%7C0499d7fe3fd97c79cefda4d96eb98156;
path=/testjmeter/; httponly
*http://authnet.danielwatrous.com/testjmeter/wp-admin/*
Set-Cookie:
wp-settings-1=m8%3Dc%26m6%3Dc%26m10%3Dc%26m11%3Do%26m7%3Do%26m4%3Dc%26m12%3Dc%26m0%3Dc%26m1%3Dc;
expires=Sat, 02-Jun-2012 00:40:23 GMT; path=/testjmeter/
Set-Cookie: wp-settings-time-1=1307061623; expires=Sat, 02-Jun-2012 00:40:23
GMT; path=/testjmeter/
Atleast the browser behaves correctly - as far as I remember setting the
expiry date to the past is equivalent to deleting the cookie - so if you set
expiry in the past , then the browser wont send the cookie either
regards
deepak
On Thu, Jun 2, 2011 at 5:30 PM, Daniel Watrous wrote:
> Did any of you notice that the Date of the request is accurate and so
> are some of the cookies? WordPress seems to deliberately send the
> login related cookies with the year old expiration. Others are fine.
>
> I mention this because there seems to be an idea that the server time
> is configured wrong.
>
> On Thu, Jun 2, 2011 at 4:32 PM, sebb wrote:
> > On 2 June 2011 17:26, Bruce Ide wrote:
> >> > I think it's a bit premature to suggest that WordPress is broken. It
> >> > is used on tens of millions of sites and people are able to login
> fine
> >> >every day.
> >>
> >> Number of users is not a quality metric! Look at Windows... (Heh heh
> heh)
> >>
> >>> Well there's your problem!
> >>>
> >>> That only affects the cookies that are stored in the cookies file
> >>> (which is not normally used).
> >>>
> >>>
> >> Doh! It seemed like such a likely culprit, too!
> >>
> >
> > The actual expiry code is similar:
> >
> >// Store session cookies as well as unexpired ones
> >if (exp == 0 || exp >= System.currentTimeMillis()) {
> >newCookie.setVersion(cookie.getVersion());
> >add(newCookie); // Has its own debug log; removes
> > matching cookies
> >} else {
> >removeMatchingCookies(newCookie);
> >if (debugEnabled){
> >log.debug("Dropping expired Cookie:
> > "+newCookie.toString());
> >}
> >}
> >
> >
> >>
> >>> > I'd be really hesitant to change the behavior of the test environment
> to
> >>> > mask a bug you uncovered, though. Sending expired cookies IS a bug,
> and
> >>> it's
> >>> > something the guys running the server should fix.
> >>>
> >>> If this is a general problem, I suppose it might make sense to add an
> >>> option to remove the expiry date from stale cookies, turning them into
> >>> session cookies.
> >>> But AFAIK this is the first time this has been reported [, and might
> >>> cause indigestion (!) in some cases].
> >>>
> >>>
> >> Well it sounds like the web browser is also storing and using the
> expired
> >> cookie, and the remote server is honoring it! That's like 3 different
> bugs
> >> he's uncovered so far! At this point I'd be rampaging like... something
> that
> >> rampages a LOT... through 2 or 3 different bug forums.
> >>
> >> I'm sure the Firefox guys would say "No it's not!" At least some people
> in
> >> the "real world" do check cookie expiry dates, but it's probably
> "optional".
> >> I'm not inclined to go digging through RFCs to find out.
> >>
> >> I'd say Wordpress sending out cookies from last year means someone
> hasn't
> >> been minding a server like they should be. That really IS a problem.
> >
> > Agreed.
> >
> >> I suppose you could add a "Remove expiration dates" to the cookie
> manager
> >> panel, or a "send expired cookies" checkbox to the httpclient. Probably
> &g
Re: cookie manager not working
Did any of you notice that the Date of the request is accurate and so
are some of the cookies? WordPress seems to deliberately send the
login related cookies with the year old expiration. Others are fine.
I mention this because there seems to be an idea that the server time
is configured wrong.
On Thu, Jun 2, 2011 at 4:32 PM, sebb wrote:
> On 2 June 2011 17:26, Bruce Ide wrote:
>> > I think it's a bit premature to suggest that WordPress is broken. It
>> > is used on tens of millions of sites and people are able to login fine
>> >every day.
>>
>> Number of users is not a quality metric! Look at Windows... (Heh heh heh)
>>
>>> Well there's your problem!
>>>
>>> That only affects the cookies that are stored in the cookies file
>>> (which is not normally used).
>>>
>>>
>> Doh! It seemed like such a likely culprit, too!
>>
>
> The actual expiry code is similar:
>
> // Store session cookies as well as unexpired ones
> if (exp == 0 || exp >= System.currentTimeMillis()) {
> newCookie.setVersion(cookie.getVersion());
> add(newCookie); // Has its own debug log; removes
> matching cookies
> } else {
> removeMatchingCookies(newCookie);
> if (debugEnabled){
> log.debug("Dropping expired Cookie:
> "+newCookie.toString());
> }
> }
>
>
>>
>>> > I'd be really hesitant to change the behavior of the test environment to
>>> > mask a bug you uncovered, though. Sending expired cookies IS a bug, and
>>> it's
>>> > something the guys running the server should fix.
>>>
>>> If this is a general problem, I suppose it might make sense to add an
>>> option to remove the expiry date from stale cookies, turning them into
>>> session cookies.
>>> But AFAIK this is the first time this has been reported [, and might
>>> cause indigestion (!) in some cases].
>>>
>>>
>> Well it sounds like the web browser is also storing and using the expired
>> cookie, and the remote server is honoring it! That's like 3 different bugs
>> he's uncovered so far! At this point I'd be rampaging like... something that
>> rampages a LOT... through 2 or 3 different bug forums.
>>
>> I'm sure the Firefox guys would say "No it's not!" At least some people in
>> the "real world" do check cookie expiry dates, but it's probably "optional".
>> I'm not inclined to go digging through RFCs to find out.
>>
>> I'd say Wordpress sending out cookies from last year means someone hasn't
>> been minding a server like they should be. That really IS a problem.
>
> Agreed.
>
>> I suppose you could add a "Remove expiration dates" to the cookie manager
>> panel, or a "send expired cookies" checkbox to the httpclient. Probably
>> wouldn't be a huge amount of coding, and would probably be only vaguely
>> atrocious.
>
> It's fairly simple to change the code itself, but there is additional
> work needed to implement the GUI change and update the documentation.
>
> It's not yet clear if this is a general problem affecting multiple
> servers, or just WordPress servers, or just an issue with the
> particular WordPress host.
>
>> Or perhaps a sampler or postprocessor that allows you to manipulate explicit
>> cookie values? That'd be a bit more work, but might be more palatable.
>
> That can be done already with the Regex Processor and Header Manager,
> or using the BSH or BSF test elements.
>
> Might just be simpler to change the time on the box running JMeter ...
>
> -
> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
>
>
-
To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
On 2 June 2011 17:26, Bruce Ide wrote:
> > I think it's a bit premature to suggest that WordPress is broken. It
> > is used on tens of millions of sites and people are able to login fine
> >every day.
>
> Number of users is not a quality metric! Look at Windows... (Heh heh heh)
>
>> Well there's your problem!
>>
>> That only affects the cookies that are stored in the cookies file
>> (which is not normally used).
>>
>>
> Doh! It seemed like such a likely culprit, too!
>
The actual expiry code is similar:
// Store session cookies as well as unexpired ones
if (exp == 0 || exp >= System.currentTimeMillis()) {
newCookie.setVersion(cookie.getVersion());
add(newCookie); // Has its own debug log; removes
matching cookies
} else {
removeMatchingCookies(newCookie);
if (debugEnabled){
log.debug("Dropping expired Cookie:
"+newCookie.toString());
}
}
>
>> > I'd be really hesitant to change the behavior of the test environment to
>> > mask a bug you uncovered, though. Sending expired cookies IS a bug, and
>> it's
>> > something the guys running the server should fix.
>>
>> If this is a general problem, I suppose it might make sense to add an
>> option to remove the expiry date from stale cookies, turning them into
>> session cookies.
>> But AFAIK this is the first time this has been reported [, and might
>> cause indigestion (!) in some cases].
>>
>>
> Well it sounds like the web browser is also storing and using the expired
> cookie, and the remote server is honoring it! That's like 3 different bugs
> he's uncovered so far! At this point I'd be rampaging like... something that
> rampages a LOT... through 2 or 3 different bug forums.
>
> I'm sure the Firefox guys would say "No it's not!" At least some people in
> the "real world" do check cookie expiry dates, but it's probably "optional".
> I'm not inclined to go digging through RFCs to find out.
>
> I'd say Wordpress sending out cookies from last year means someone hasn't
> been minding a server like they should be. That really IS a problem.
Agreed.
> I suppose you could add a "Remove expiration dates" to the cookie manager
> panel, or a "send expired cookies" checkbox to the httpclient. Probably
> wouldn't be a huge amount of coding, and would probably be only vaguely
> atrocious.
It's fairly simple to change the code itself, but there is additional
work needed to implement the GUI change and update the documentation.
It's not yet clear if this is a general problem affecting multiple
servers, or just WordPress servers, or just an issue with the
particular WordPress host.
> Or perhaps a sampler or postprocessor that allows you to manipulate explicit
> cookie values? That'd be a bit more work, but might be more palatable.
That can be done already with the Regex Processor and Header Manager,
or using the BSH or BSF test elements.
Might just be simpler to change the time on the box running JMeter ...
-
To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
> I think it's a bit premature to suggest that WordPress is broken. It > is used on tens of millions of sites and people are able to login fine >every day. Number of users is not a quality metric! Look at Windows... (Heh heh heh) > Well there's your problem! > > That only affects the cookies that are stored in the cookies file > (which is not normally used). > > Doh! It seemed like such a likely culprit, too! > > I'd be really hesitant to change the behavior of the test environment to > > mask a bug you uncovered, though. Sending expired cookies IS a bug, and > it's > > something the guys running the server should fix. > > If this is a general problem, I suppose it might make sense to add an > option to remove the expiry date from stale cookies, turning them into > session cookies. > But AFAIK this is the first time this has been reported [, and might > cause indigestion (!) in some cases]. > > Well it sounds like the web browser is also storing and using the expired cookie, and the remote server is honoring it! That's like 3 different bugs he's uncovered so far! At this point I'd be rampaging like... something that rampages a LOT... through 2 or 3 different bug forums. I'm sure the Firefox guys would say "No it's not!" At least some people in the "real world" do check cookie expiry dates, but it's probably "optional". I'm not inclined to go digging through RFCs to find out. I'd say Wordpress sending out cookies from last year means someone hasn't been minding a server like they should be. That really IS a problem. I suppose you could add a "Remove expiration dates" to the cookie manager panel, or a "send expired cookies" checkbox to the httpclient. Probably wouldn't be a huge amount of coding, and would probably be only vaguely atrocious. Or perhaps a sampler or postprocessor that allows you to manipulate explicit cookie values? That'd be a bit more work, but might be more palatable. -- Bruce Ide flyingrhenqu...@gmail.com
Re: cookie manager not working
On 2 June 2011 16:35, Bruce Ide wrote:
> Jmeter's doing the right thing. If you're testing wordpress, file a bug with
> them and tell them to fix their thing. If you're running an application
> server yourself, I'd suspect it's something wrong with your application
> server config.
I'm inclined to agree - as far as I can tell, session cookies are
cookies without an expiry date or age.
> You have the jmeter source, you could always change its behavior to do what
> you want and recompile it. I'd start with CookieManager.java:
>
> while (cookies.hasNext()) {
> Cookie cook = (Cookie) cookies.next().getObjectValue();
> final long expiresMillis = cook.getExpiresMillis();
> if (expiresMillis == 0 || expiresMillis > now) { // only save
> unexpired cookies
> writer.println(cookieToString(cook));
> }
> }
>
> Well there's your problem!
That only affects the cookies that are stored in the cookies file
(which is not normally used).
> I can't guarantee that's the only thing that
> prevents expired cookies from being sent. I suspect there's probably also
> some code in httpclient that checks to see if they're expired before sending
> them back.
Yes.
JMeter currently uses the Commons HttpClient 3.1 cookie handling code.
> I'd be really hesitant to change the behavior of the test environment to
> mask a bug you uncovered, though. Sending expired cookies IS a bug, and it's
> something the guys running the server should fix.
If this is a general problem, I suppose it might make sense to add an
option to remove the expiry date from stale cookies, turning them into
session cookies.
But AFAIK this is the first time this has been reported [, and might
cause indigestion (!) in some cases].
Note that cookies won't be handled properly if you have selected
"redirect automatically", because then JMeter does not see the cookies
> --
> Bruce Ide
> flyingrhenqu...@gmail.com
>
-
To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
I think it's a bit premature to suggest that WordPress is broken. It
is used on tens of millions of sites and people are able to login fine
every day.
Is there a jobs board for jmeter where I could hire a guru to get my
tests going?
Daniel
On Thu, Jun 2, 2011 at 9:35 AM, Bruce Ide wrote:
> Jmeter's doing the right thing. If you're testing wordpress, file a bug with
> them and tell them to fix their thing. If you're running an application
> server yourself, I'd suspect it's something wrong with your application
> server config.
>
> You have the jmeter source, you could always change its behavior to do what
> you want and recompile it. I'd start with CookieManager.java:
>
> while (cookies.hasNext()) {
> Cookie cook = (Cookie) cookies.next().getObjectValue();
> final long expiresMillis = cook.getExpiresMillis();
> if (expiresMillis == 0 || expiresMillis > now) { // only save
> unexpired cookies
> writer.println(cookieToString(cook));
> }
> }
>
> Well there's your problem! I can't guarantee that's the only thing that
> prevents expired cookies from being sent. I suspect there's probably also
> some code in httpclient that checks to see if they're expired before sending
> them back.
>
> I'd be really hesitant to change the behavior of the test environment to
> mask a bug you uncovered, though. Sending expired cookies IS a bug, and it's
> something the guys running the server should fix.
>
> --
> Bruce Ide
> flyingrhenqu...@gmail.com
>
-
To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
Jmeter's doing the right thing. If you're testing wordpress, file a bug with
them and tell them to fix their thing. If you're running an application
server yourself, I'd suspect it's something wrong with your application
server config.
You have the jmeter source, you could always change its behavior to do what
you want and recompile it. I'd start with CookieManager.java:
while (cookies.hasNext()) {
Cookie cook = (Cookie) cookies.next().getObjectValue();
final long expiresMillis = cook.getExpiresMillis();
if (expiresMillis == 0 || expiresMillis > now) { // only save
unexpired cookies
writer.println(cookieToString(cook));
}
}
Well there's your problem! I can't guarantee that's the only thing that
prevents expired cookies from being sent. I suspect there's probably also
some code in httpclient that checks to see if they're expired before sending
them back.
I'd be really hesitant to change the behavior of the test environment to
mask a bug you uncovered, though. Sending expired cookies IS a bug, and it's
something the guys running the server should fix.
--
Bruce Ide
flyingrhenqu...@gmail.com
Re: cookie manager not working
I'm still struggling with this. I've made the following video that will hopefully give enough detail to help me along: http://www.screencast.com/t/Dafijet8P9VS I've also created a test site if that helps you troubleshoot this issue with me. http://authnet.danielwatrous.com/testjmeter/ username: admin password: test The log file had to do with permissions. When I moved the jmeter files outside of the program files folder it was able to create the log file. Thank you. On Wed, Jun 1, 2011 at 7:40 PM, sebb wrote: > On 2 June 2011 02:06, Daniel Watrous wrote: >> I've discovered that the cookies sent back by wordpress have an >> expires value one year before the date of the request. Browsers seem >> to store this as a session cookie, but I'm not sure why. Is there some >> way to tell the cookie manager to deal with these cookies that have an >> expires value before right now? > > No, not without modifying JMeter code. > However, by judicious use of the Regex Extractor you should be able to > extract the cookie from the header and then add it using a Header > Manager. > >> I've put in a post on the wordpress forum to figure out why they do it that >> way. >> >> I also can't find a log file. How can I troubleshoot the reason a log >> file won't write? > > Check if the launch directory is writable. Are you sure there is no > jmeter.log file? > >> Daniel >> >> On Fri, May 27, 2011 at 7:29 AM, sebb wrote: >>> On 27 May 2011 14:17, Daniel Watrous wrote: >>>> I had actually tried that before mailing to the list. I just tried it >>>> again with no change to whether cookies are sent or not. >>> >>> In that case, you'll need to enable debug logging for the Cookie >>> Manager: select it and use the Menu item Help/Enable Debug >>> >>> Output will be in the log file. >>> >>>> I can't find the log file, but here's my java version: >>> >>> Unless you override the location in the jmeter.properties file, the >>> log file will be in the directory where you started JMeter from, by >>> default the bin directory, and will be called jmeter.log. >>> >>>> C:\Program Files (x86)\Console2>java -version >>>> java version "1.6.0_20" >>>> Java(TM) SE Runtime Environment (build 1.6.0_20-b02) >>>> Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing) >>>> >>>> C:\Program Files (x86)\Console2> >>>> >>>> Windows 7 x64 >>>> >>>> thanks, >>>> >>>> Daniel >>>> >>>> >>>> >>>> On Fri, May 27, 2011 at 3:03 AM, sebb wrote: >>>>> On 27 May 2011 08:48, sebb wrote: >>>>>> On 27 May 2011 06:47, Daniel Watrous wrote: >>>>>>> Hello, >>>>>>> >>>>>>> I've been trying to setup a jmeter program to test a wordpress plugin. >>>>>>> However, I can't get the login to work. It appears to be sending the >>>>>>> cookies back correctly when the login is sent, but they don't get >>>>>>> picked up by the cookie manager. >>>>>>> >>>>>>> I've been searching for a while and looked at dozens of examples. >>>>>>> Maybe you can spot what I've done wrong from these screenshots: >>>>>>> >>>>>>> http://screencast.com/t/EW1zAgvlK >>>>>>> http://screencast.com/t/2i8dTyBh >>>>>>> http://screencast.com/t/fd5dGPvCb >>>>>> >>>>>> The Cookie Manager is set to require RFC2109 cookies; these have a >>>>>> specific format that is not always followed by servers (or browsers). >>>>>> >>>>>> The default is supposed to be "compatibility" mode, try using that. >>>>>> >>>>>> What version of Java are you using? This will be shown near the start >>>>>> of the jmeter.log file, e.g. >>>>>> >>>>>> java.version=1.5.0_22 >>>>>> java.vm.name=Java HotSpot(TM) Client VM >>>>>> >>>>>> I've just noticed that the default when adding a new Cookie Manager is >>>>>> set correctly to "compatibility" (first option) when using that >>>>> >>>>> Actually it's the last option when using Java 1.5, first when using >>>>> 1.6 - which is whe
Re: cookie manager not working
On 2 June 2011 02:06, Daniel Watrous wrote: > I've discovered that the cookies sent back by wordpress have an > expires value one year before the date of the request. Browsers seem > to store this as a session cookie, but I'm not sure why. Is there some > way to tell the cookie manager to deal with these cookies that have an > expires value before right now? No, not without modifying JMeter code. However, by judicious use of the Regex Extractor you should be able to extract the cookie from the header and then add it using a Header Manager. > I've put in a post on the wordpress forum to figure out why they do it that > way. > > I also can't find a log file. How can I troubleshoot the reason a log > file won't write? Check if the launch directory is writable. Are you sure there is no jmeter.log file? > Daniel > > On Fri, May 27, 2011 at 7:29 AM, sebb wrote: >> On 27 May 2011 14:17, Daniel Watrous wrote: >>> I had actually tried that before mailing to the list. I just tried it >>> again with no change to whether cookies are sent or not. >> >> In that case, you'll need to enable debug logging for the Cookie >> Manager: select it and use the Menu item Help/Enable Debug >> >> Output will be in the log file. >> >>> I can't find the log file, but here's my java version: >> >> Unless you override the location in the jmeter.properties file, the >> log file will be in the directory where you started JMeter from, by >> default the bin directory, and will be called jmeter.log. >> >>> C:\Program Files (x86)\Console2>java -version >>> java version "1.6.0_20" >>> Java(TM) SE Runtime Environment (build 1.6.0_20-b02) >>> Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing) >>> >>> C:\Program Files (x86)\Console2> >>> >>> Windows 7 x64 >>> >>> thanks, >>> >>> Daniel >>> >>> >>> >>> On Fri, May 27, 2011 at 3:03 AM, sebb wrote: >>>> On 27 May 2011 08:48, sebb wrote: >>>>> On 27 May 2011 06:47, Daniel Watrous wrote: >>>>>> Hello, >>>>>> >>>>>> I've been trying to setup a jmeter program to test a wordpress plugin. >>>>>> However, I can't get the login to work. It appears to be sending the >>>>>> cookies back correctly when the login is sent, but they don't get >>>>>> picked up by the cookie manager. >>>>>> >>>>>> I've been searching for a while and looked at dozens of examples. >>>>>> Maybe you can spot what I've done wrong from these screenshots: >>>>>> >>>>>> http://screencast.com/t/EW1zAgvlK >>>>>> http://screencast.com/t/2i8dTyBh >>>>>> http://screencast.com/t/fd5dGPvCb >>>>> >>>>> The Cookie Manager is set to require RFC2109 cookies; these have a >>>>> specific format that is not always followed by servers (or browsers). >>>>> >>>>> The default is supposed to be "compatibility" mode, try using that. >>>>> >>>>> What version of Java are you using? This will be shown near the start >>>>> of the jmeter.log file, e.g. >>>>> >>>>> java.version=1.5.0_22 >>>>> java.vm.name=Java HotSpot(TM) Client VM >>>>> >>>>> I've just noticed that the default when adding a new Cookie Manager is >>>>> set correctly to "compatibility" (first option) when using that >>>> >>>> Actually it's the last option when using Java 1.5, first when using >>>> 1.6 - which is where the problem lies ... >>>> >>>>> version, however when using >>>>> >>>>> java.version=1.6.0_25 >>>>> java.vm.name=Java HotSpot(TM) Client VM >>>>> >>>>> which is the current Java version it is set to "rfc109" (the last option). >>>>> >>>>> This is odd, since the code specifically tries to set "compatibility" >>>>> mode. >>>>> Looks like there may be a Java bug (or at least a change in behaviour). >>>> >>>> It's a change in Java behaviour - the order of cookie policies is >>>> different, because of internal changes to the libraries. >>>> >>>> JMeter incorrectly relies on the order of the entries. Oops. >>>> >>>
Re: cookie manager not working
I've discovered that the cookies sent back by wordpress have an expires value one year before the date of the request. Browsers seem to store this as a session cookie, but I'm not sure why. Is there some way to tell the cookie manager to deal with these cookies that have an expires value before right now? I've put in a post on the wordpress forum to figure out why they do it that way. I also can't find a log file. How can I troubleshoot the reason a log file won't write? Daniel On Fri, May 27, 2011 at 7:29 AM, sebb wrote: > On 27 May 2011 14:17, Daniel Watrous wrote: >> I had actually tried that before mailing to the list. I just tried it >> again with no change to whether cookies are sent or not. > > In that case, you'll need to enable debug logging for the Cookie > Manager: select it and use the Menu item Help/Enable Debug > > Output will be in the log file. > >> I can't find the log file, but here's my java version: > > Unless you override the location in the jmeter.properties file, the > log file will be in the directory where you started JMeter from, by > default the bin directory, and will be called jmeter.log. > >> C:\Program Files (x86)\Console2>java -version >> java version "1.6.0_20" >> Java(TM) SE Runtime Environment (build 1.6.0_20-b02) >> Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing) >> >> C:\Program Files (x86)\Console2> >> >> Windows 7 x64 >> >> thanks, >> >> Daniel >> >> >> >> On Fri, May 27, 2011 at 3:03 AM, sebb wrote: >>> On 27 May 2011 08:48, sebb wrote: >>>> On 27 May 2011 06:47, Daniel Watrous wrote: >>>>> Hello, >>>>> >>>>> I've been trying to setup a jmeter program to test a wordpress plugin. >>>>> However, I can't get the login to work. It appears to be sending the >>>>> cookies back correctly when the login is sent, but they don't get >>>>> picked up by the cookie manager. >>>>> >>>>> I've been searching for a while and looked at dozens of examples. >>>>> Maybe you can spot what I've done wrong from these screenshots: >>>>> >>>>> http://screencast.com/t/EW1zAgvlK >>>>> http://screencast.com/t/2i8dTyBh >>>>> http://screencast.com/t/fd5dGPvCb >>>> >>>> The Cookie Manager is set to require RFC2109 cookies; these have a >>>> specific format that is not always followed by servers (or browsers). >>>> >>>> The default is supposed to be "compatibility" mode, try using that. >>>> >>>> What version of Java are you using? This will be shown near the start >>>> of the jmeter.log file, e.g. >>>> >>>> java.version=1.5.0_22 >>>> java.vm.name=Java HotSpot(TM) Client VM >>>> >>>> I've just noticed that the default when adding a new Cookie Manager is >>>> set correctly to "compatibility" (first option) when using that >>> >>> Actually it's the last option when using Java 1.5, first when using >>> 1.6 - which is where the problem lies ... >>> >>>> version, however when using >>>> >>>> java.version=1.6.0_25 >>>> java.vm.name=Java HotSpot(TM) Client VM >>>> >>>> which is the current Java version it is set to "rfc109" (the last option). >>>> >>>> This is odd, since the code specifically tries to set "compatibility" mode. >>>> Looks like there may be a Java bug (or at least a change in behaviour). >>> >>> It's a change in Java behaviour - the order of cookie policies is >>> different, because of internal changes to the libraries. >>> >>> JMeter incorrectly relies on the order of the entries. Oops. >>> >>> However, there's an easy work-round - just change the policy to >>> compatibility. >>> >>>> >>>>> Thanks in advance. >>>>> >>>>> Daniel >>>>> >>>>> - >>>>> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >>>>> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >>>>> >>>>> >>>> >>> >>> - >>> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >>> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >>> >>> >> >> - >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
On 27 May 2011 14:17, Daniel Watrous wrote: > I had actually tried that before mailing to the list. I just tried it > again with no change to whether cookies are sent or not. In that case, you'll need to enable debug logging for the Cookie Manager: select it and use the Menu item Help/Enable Debug Output will be in the log file. > I can't find the log file, but here's my java version: Unless you override the location in the jmeter.properties file, the log file will be in the directory where you started JMeter from, by default the bin directory, and will be called jmeter.log. > C:\Program Files (x86)\Console2>java -version > java version "1.6.0_20" > Java(TM) SE Runtime Environment (build 1.6.0_20-b02) > Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing) > > C:\Program Files (x86)\Console2> > > Windows 7 x64 > > thanks, > > Daniel > > > > On Fri, May 27, 2011 at 3:03 AM, sebb wrote: >> On 27 May 2011 08:48, sebb wrote: >>> On 27 May 2011 06:47, Daniel Watrous wrote: >>>> Hello, >>>> >>>> I've been trying to setup a jmeter program to test a wordpress plugin. >>>> However, I can't get the login to work. It appears to be sending the >>>> cookies back correctly when the login is sent, but they don't get >>>> picked up by the cookie manager. >>>> >>>> I've been searching for a while and looked at dozens of examples. >>>> Maybe you can spot what I've done wrong from these screenshots: >>>> >>>> http://screencast.com/t/EW1zAgvlK >>>> http://screencast.com/t/2i8dTyBh >>>> http://screencast.com/t/fd5dGPvCb >>> >>> The Cookie Manager is set to require RFC2109 cookies; these have a >>> specific format that is not always followed by servers (or browsers). >>> >>> The default is supposed to be "compatibility" mode, try using that. >>> >>> What version of Java are you using? This will be shown near the start >>> of the jmeter.log file, e.g. >>> >>> java.version=1.5.0_22 >>> java.vm.name=Java HotSpot(TM) Client VM >>> >>> I've just noticed that the default when adding a new Cookie Manager is >>> set correctly to "compatibility" (first option) when using that >> >> Actually it's the last option when using Java 1.5, first when using >> 1.6 - which is where the problem lies ... >> >>> version, however when using >>> >>> java.version=1.6.0_25 >>> java.vm.name=Java HotSpot(TM) Client VM >>> >>> which is the current Java version it is set to "rfc109" (the last option). >>> >>> This is odd, since the code specifically tries to set "compatibility" mode. >>> Looks like there may be a Java bug (or at least a change in behaviour). >> >> It's a change in Java behaviour - the order of cookie policies is >> different, because of internal changes to the libraries. >> >> JMeter incorrectly relies on the order of the entries. Oops. >> >> However, there's an easy work-round - just change the policy to >> compatibility. >> >>> >>>> Thanks in advance. >>>> >>>> Daniel >>>> >>>> - >>>> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >>>> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >>>> >>>> >>> >> >> - >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
I had actually tried that before mailing to the list. I just tried it again with no change to whether cookies are sent or not. I can't find the log file, but here's my java version: C:\Program Files (x86)\Console2>java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing) C:\Program Files (x86)\Console2> Windows 7 x64 thanks, Daniel On Fri, May 27, 2011 at 3:03 AM, sebb wrote: > On 27 May 2011 08:48, sebb wrote: >> On 27 May 2011 06:47, Daniel Watrous wrote: >>> Hello, >>> >>> I've been trying to setup a jmeter program to test a wordpress plugin. >>> However, I can't get the login to work. It appears to be sending the >>> cookies back correctly when the login is sent, but they don't get >>> picked up by the cookie manager. >>> >>> I've been searching for a while and looked at dozens of examples. >>> Maybe you can spot what I've done wrong from these screenshots: >>> >>> http://screencast.com/t/EW1zAgvlK >>> http://screencast.com/t/2i8dTyBh >>> http://screencast.com/t/fd5dGPvCb >> >> The Cookie Manager is set to require RFC2109 cookies; these have a >> specific format that is not always followed by servers (or browsers). >> >> The default is supposed to be "compatibility" mode, try using that. >> >> What version of Java are you using? This will be shown near the start >> of the jmeter.log file, e.g. >> >> java.version=1.5.0_22 >> java.vm.name=Java HotSpot(TM) Client VM >> >> I've just noticed that the default when adding a new Cookie Manager is >> set correctly to "compatibility" (first option) when using that > > Actually it's the last option when using Java 1.5, first when using > 1.6 - which is where the problem lies ... > >> version, however when using >> >> java.version=1.6.0_25 >> java.vm.name=Java HotSpot(TM) Client VM >> >> which is the current Java version it is set to "rfc109" (the last option). >> >> This is odd, since the code specifically tries to set "compatibility" mode. >> Looks like there may be a Java bug (or at least a change in behaviour). > > It's a change in Java behaviour - the order of cookie policies is > different, because of internal changes to the libraries. > > JMeter incorrectly relies on the order of the entries. Oops. > > However, there's an easy work-round - just change the policy to compatibility. > >> >>> Thanks in advance. >>> >>> Daniel >>> >>> - >>> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >>> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >>> >>> >> > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
On 27 May 2011 08:48, sebb wrote: > On 27 May 2011 06:47, Daniel Watrous wrote: >> Hello, >> >> I've been trying to setup a jmeter program to test a wordpress plugin. >> However, I can't get the login to work. It appears to be sending the >> cookies back correctly when the login is sent, but they don't get >> picked up by the cookie manager. >> >> I've been searching for a while and looked at dozens of examples. >> Maybe you can spot what I've done wrong from these screenshots: >> >> http://screencast.com/t/EW1zAgvlK >> http://screencast.com/t/2i8dTyBh >> http://screencast.com/t/fd5dGPvCb > > The Cookie Manager is set to require RFC2109 cookies; these have a > specific format that is not always followed by servers (or browsers). > > The default is supposed to be "compatibility" mode, try using that. > > What version of Java are you using? This will be shown near the start > of the jmeter.log file, e.g. > > java.version=1.5.0_22 > java.vm.name=Java HotSpot(TM) Client VM > > I've just noticed that the default when adding a new Cookie Manager is > set correctly to "compatibility" (first option) when using that Actually it's the last option when using Java 1.5, first when using 1.6 - which is where the problem lies ... > version, however when using > > java.version=1.6.0_25 > java.vm.name=Java HotSpot(TM) Client VM > > which is the current Java version it is set to "rfc109" (the last option). > > This is odd, since the code specifically tries to set "compatibility" mode. > Looks like there may be a Java bug (or at least a change in behaviour). It's a change in Java behaviour - the order of cookie policies is different, because of internal changes to the libraries. JMeter incorrectly relies on the order of the entries. Oops. However, there's an easy work-round - just change the policy to compatibility. > >> Thanks in advance. >> >> Daniel >> >> - >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: cookie manager not working
On 27 May 2011 06:47, Daniel Watrous wrote: > Hello, > > I've been trying to setup a jmeter program to test a wordpress plugin. > However, I can't get the login to work. It appears to be sending the > cookies back correctly when the login is sent, but they don't get > picked up by the cookie manager. > > I've been searching for a while and looked at dozens of examples. > Maybe you can spot what I've done wrong from these screenshots: > > http://screencast.com/t/EW1zAgvlK > http://screencast.com/t/2i8dTyBh > http://screencast.com/t/fd5dGPvCb The Cookie Manager is set to require RFC2109 cookies; these have a specific format that is not always followed by servers (or browsers). The default is supposed to be "compatibility" mode, try using that. What version of Java are you using? This will be shown near the start of the jmeter.log file, e.g. java.version=1.5.0_22 java.vm.name=Java HotSpot(TM) Client VM I've just noticed that the default when adding a new Cookie Manager is set correctly to "compatibility" (first option) when using that version, however when using java.version=1.6.0_25 java.vm.name=Java HotSpot(TM) Client VM which is the current Java version it is set to "rfc109" (the last option). This is odd, since the code specifically tries to set "compatibility" mode. Looks like there may be a Java bug (or at least a change in behaviour). > Thanks in advance. > > Daniel > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
cookie manager not working
Hello, I've been trying to setup a jmeter program to test a wordpress plugin. However, I can't get the login to work. It appears to be sending the cookies back correctly when the login is sent, but they don't get picked up by the cookie manager. I've been searching for a while and looked at dozens of examples. Maybe you can spot what I've done wrong from these screenshots: http://screencast.com/t/EW1zAgvlK http://screencast.com/t/2i8dTyBh http://screencast.com/t/fd5dGPvCb Thanks in advance. Daniel - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: Cookie Manager woes
possibly you havent specified the data correctly in the Cookie Manager e.g. domain should be blah.com (exactly) path should be / or /blah secure should be blank On Thu, May 13, 2010 at 7:39 AM, jacobd wrote: > > Hey everyone. > > Im having trouble with using the cookie manager jmeter. > > Im using jmeter 2.3.4 > > When I setup up the cookie manager in my thread group I cant seem to send > any cookies even with setting one manually. As well as not setting any > manually when I look at the request in the tree view it shows the > following: > > GET http://blah.com/blah/blah=blah <-- > just an example request. > > [no cookies] > > Request Headers: > Connection: keep-alive > > My setup is as follows: > > test plan > -Thread Group > - HTTP request > - Cookie Manager > Simple Data writer > > > > Am I missing something in the config file? > > Thanks, > Jacob > -- > View this message in context: > http://old.nabble.com/Cookie-Manager-woes-tp28548416p28548416.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
Cookie Manager woes
Hey everyone. Im having trouble with using the cookie manager jmeter. Im using jmeter 2.3.4 When I setup up the cookie manager in my thread group I cant seem to send any cookies even with setting one manually. As well as not setting any manually when I look at the request in the tree view it shows the following: GET http://blah.com/blah/blah=blah <-- just an example request. [no cookies] Request Headers: Connection: keep-alive My setup is as follows: test plan -Thread Group - HTTP request - Cookie Manager Simple Data writer Am I missing something in the config file? Thanks, Jacob -- View this message in context: http://old.nabble.com/Cookie-Manager-woes-tp28548416p28548416.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: Setting Host header interferes with cookie manager
> > Two DNS names , even if they map to the same IP address arent the same > for cookies. I agree that's where I'm running into problems. The requirements for the Host header [1] says it specifies the Internet host of the resource being requested, as obtained from the original URI. In jmeter, I guess the "original URL" is the server name/IP field + path, which would make sense. I thought I could use the server name/IP field only for where to connect and have the cookie manager look at the Host field for the cookies, but I guess it doesn't work that way. /etc/hosts is it. [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23
Re: Setting Host header interferes with cookie manager
>More importantly, it's the exact same cookie domain >and path if I use the server IP or name. It appears the cookie manager won't >*send* it if I'm using the IP. and that behavior is correct. It is exactly how your browser would behave as well. Two DNS names , even if they map to the same IP address arent the same for cookies. Technically your application should not be setting cookies based on the host header , it should be based on what the user has typed in their browser. Other than a beanshell script that would copy the cookie to the IP address , I dont see how you could get this to work without actually requesting the DNS name from Jmeter (or an entry in the hosts file on the jmeter machine) regards deepak On Wed, Dec 23, 2009 at 11:27 AM, Trenton Lipscomb wrote: > > I guesss the cookie is tied to the domain it receives (if you access a > site > > using Internet explorer with the IP address and get a cookie and then > > access > > it again but this time type the DNS , the browser will not send the > > cookie). > > > > Agreed, but that's slightly different that what I'm doing. That scenario > would be analogous for using an IP in the Host header. > > > > if you add a view results tree listener and check the Set-Cookie you > > receive > > does it have a domain? > > > > It does. It's the exact same as the Host I'm requesting > > domain=.beta.mysite.com > > That would make sense, since it's Apache setting the cookie and it knows > which vhost I requested. More importantly, it's the exact same cookie > domain > and path if I use the server IP or name. It appears the cookie manager > won't > *send* it if I'm using the IP. Perhaps it's using the server name as the > key > and not the Host header? > > > > Also if you dont add a host header and just request using IP address what > > happens? > > > > Won't work because I have the site configured as a virtual host. It must > get > that Host header to know which host/docroot I want. >
Re: Setting Host header interferes with cookie manager
> I guesss the cookie is tied to the domain it receives (if you access a site > using Internet explorer with the IP address and get a cookie and then > access > it again but this time type the DNS , the browser will not send the > cookie). > Agreed, but that's slightly different that what I'm doing. That scenario would be analogous for using an IP in the Host header. > if you add a view results tree listener and check the Set-Cookie you > receive > does it have a domain? > It does. It's the exact same as the Host I'm requesting domain=.beta.mysite.com That would make sense, since it's Apache setting the cookie and it knows which vhost I requested. More importantly, it's the exact same cookie domain and path if I use the server IP or name. It appears the cookie manager won't *send* it if I'm using the IP. Perhaps it's using the server name as the key and not the Host header? > Also if you dont add a host header and just request using IP address what > happens? > Won't work because I have the site configured as a virtual host. It must get that Host header to know which host/docroot I want.
Re: Setting Host header interferes with cookie manager
I guesss the cookie is tied to the domain it receives (if you access a site using Internet explorer with the IP address and get a cookie and then access it again but this time type the DNS , the browser will not send the cookie). if you add a view results tree listener and check the Set-Cookie you receive does it have a domain? Also if you dont add a host header and just request using IP address what happens? regards deepak On Wed, Dec 23, 2009 at 11:08 AM, Trenton Lipscomb wrote: > I'm attempting to the Host header in the header manager. I'm doing this > because the environment in which I'm testing does not have DNS... and even > if it did, I don't want to change my apache vhosts. I'd rather just send > the > right Host. > > When I specify the Host header and use an IP for the server, I don't see > cookies being sent in my requests. However, when I remove the Host header > and use a name for the server, everything works fine. > > I guess I could work around by adding an /etc/hosts entry and using a name, > but it makes my testing much less portable. > > *trenton > Sent from Wood Dale, IL, United States >
Setting Host header interferes with cookie manager
I'm attempting to the Host header in the header manager. I'm doing this because the environment in which I'm testing does not have DNS... and even if it did, I don't want to change my apache vhosts. I'd rather just send the right Host. When I specify the Host header and use an IP for the server, I don't see cookies being sent in my requests. However, when I remove the Host header and use a name for the server, everything works fine. I guess I could work around by adding an /etc/hosts entry and using a name, but it makes my testing much less portable. *trenton Sent from Wood Dale, IL, United States
Re: JMeter Cookie Manager
Hi you have to compare your browser with Jmeter's view response tree , a. Did you use redirect automatically? in which case change this to follow redirects. b. Try changing the Cookie Manager policy to see if there is any difference regards deepak On Mon, Nov 30, 2009 at 5:21 PM, cchee wrote: > > With firefox, I can see two cookies were sent back to the server. No > problem. > In regarding to your question about "same path", both use path=/ > What else do i need to check? Thanks in advance. > > > Deepak Shetty wrote: > > > > hi > > when you say same path what do you mean? > > if the path for e.g. is not specified as '/' or '/cgi-bin' in th first > > Set-Cookie then any request to the second url wont have the first cookie. > > Can you use firefox and livehttpheaders and check how your browser > > behaves? > > (It is possible that the behavior you are seeing is correct and there is > > some other issue) > > Another problem is dont use redirect automatically(cookies set here will > > not > > be handled by jmeter) , use follow redirects on the HTTP Sampler > > regards > > deepak > > > > On Wed, Nov 18, 2009 at 2:03 PM, cchee wrote: > > > >> > >> Both have the same domain and path, but different url and name. For > >> example, > >> SID (session id) from url /cgi-bin/login > >> XX_AT (authentication token) from url /cgi-bin/pin > >> > >> > >> Deepak Shetty wrote: > >> > > >> >>It seems jmeter http cookie manager only keep one cookie per domain. > >> > Not true. > >> > What do the two set-cookies look like? Note that there are domain and > >> path > >> > parameters that can be set which influence whether or not jmeter will > >> send > >> > the cookie with the request > >> > > >> > regards > >> > deepak > >> > > >> > On Wed, Nov 18, 2009 at 9:49 AM, Chester Chee > >> wrote: > >> > > >> >> > >> >> Hi, > >> >> > >> >> I am using JMeter 2.3.4 on Ubuntu 9.10 hitting a web server with web > >> apps > >> >> that uses two phases authentication. To complete the authentication, > >> two > >> >> cookies from the website (same domain) must to presented in the GET > >> >> request > >> >> to the server. > >> >> > >> >> I had debug enabled for HTTP Cookie Manager and based on the > >> information > >> >> presented in jmeter.log, I know for sure that the server did send two > >> >> Set-Cookie: with different cookie names back in its responses. And > the > >> >> jmeter log indicate both are received and store. But only one is > found > >> >> when > >> >> look up and that was the last one being sent. > >> >> > >> >> It seems jmeter http cookie manager only keep one cookie per domain. > >> >> > >> >> Is this true? If so, I don't think this the case with normal browser > >> >> nowadays. Is there a workaround for this? May be configuration > >> parameter > >> >> i > >> >> can specified to overcome this in jmeter.properties? Or this is a > bug? > >> >> Anyone experience the similar issue? > >> >> > >> >> Your kind attention and prompt responses are very much appreciated. > >> >> Thanks > >> >> in advance. > >> >> > >> >> Regards, > >> >> Chester > >> >> -- > >> >> View this message in context: > >> >> http://old.nabble.com/JMeter-Cookie-Manager-tp26412473p26412473.html > >> >> Sent from the JMeter - User mailing list archive at Nabble.com. > >> >> > >> >> > >> >> - > >> >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > >> >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >> >> > >> >> > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://old.nabble.com/Re%3A-JMeter-Cookie-Manager-tp26415243p26416606.html > >> Sent from the JMeter - User mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >> > >> > > > > > > -- > View this message in context: > http://old.nabble.com/Re%3A-JMeter-Cookie-Manager-tp26415243p26585084.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
Re: JMeter Cookie Manager
With firefox, I can see two cookies were sent back to the server. No problem. In regarding to your question about "same path", both use path=/ What else do i need to check? Thanks in advance. Deepak Shetty wrote: > > hi > when you say same path what do you mean? > if the path for e.g. is not specified as '/' or '/cgi-bin' in th first > Set-Cookie then any request to the second url wont have the first cookie. > Can you use firefox and livehttpheaders and check how your browser > behaves? > (It is possible that the behavior you are seeing is correct and there is > some other issue) > Another problem is dont use redirect automatically(cookies set here will > not > be handled by jmeter) , use follow redirects on the HTTP Sampler > regards > deepak > > On Wed, Nov 18, 2009 at 2:03 PM, cchee wrote: > >> >> Both have the same domain and path, but different url and name. For >> example, >> SID (session id) from url /cgi-bin/login >> XX_AT (authentication token) from url /cgi-bin/pin >> >> >> Deepak Shetty wrote: >> > >> >>It seems jmeter http cookie manager only keep one cookie per domain. >> > Not true. >> > What do the two set-cookies look like? Note that there are domain and >> path >> > parameters that can be set which influence whether or not jmeter will >> send >> > the cookie with the request >> > >> > regards >> > deepak >> > >> > On Wed, Nov 18, 2009 at 9:49 AM, Chester Chee >> wrote: >> > >> >> >> >> Hi, >> >> >> >> I am using JMeter 2.3.4 on Ubuntu 9.10 hitting a web server with web >> apps >> >> that uses two phases authentication. To complete the authentication, >> two >> >> cookies from the website (same domain) must to presented in the GET >> >> request >> >> to the server. >> >> >> >> I had debug enabled for HTTP Cookie Manager and based on the >> information >> >> presented in jmeter.log, I know for sure that the server did send two >> >> Set-Cookie: with different cookie names back in its responses. And the >> >> jmeter log indicate both are received and store. But only one is found >> >> when >> >> look up and that was the last one being sent. >> >> >> >> It seems jmeter http cookie manager only keep one cookie per domain. >> >> >> >> Is this true? If so, I don't think this the case with normal browser >> >> nowadays. Is there a workaround for this? May be configuration >> parameter >> >> i >> >> can specified to overcome this in jmeter.properties? Or this is a bug? >> >> Anyone experience the similar issue? >> >> >> >> Your kind attention and prompt responses are very much appreciated. >> >> Thanks >> >> in advance. >> >> >> >> Regards, >> >> Chester >> >> -- >> >> View this message in context: >> >> http://old.nabble.com/JMeter-Cookie-Manager-tp26412473p26412473.html >> >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> >> >> >> --------- >> >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://old.nabble.com/Re%3A-JMeter-Cookie-Manager-tp26415243p26416606.html >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> > > -- View this message in context: http://old.nabble.com/Re%3A-JMeter-Cookie-Manager-tp26415243p26585084.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: JMeter Cookie Manager
hi when you say same path what do you mean? if the path for e.g. is not specified as '/' or '/cgi-bin' in th first Set-Cookie then any request to the second url wont have the first cookie. Can you use firefox and livehttpheaders and check how your browser behaves? (It is possible that the behavior you are seeing is correct and there is some other issue) Another problem is dont use redirect automatically(cookies set here will not be handled by jmeter) , use follow redirects on the HTTP Sampler regards deepak On Wed, Nov 18, 2009 at 2:03 PM, cchee wrote: > > Both have the same domain and path, but different url and name. For > example, > SID (session id) from url /cgi-bin/login > XX_AT (authentication token) from url /cgi-bin/pin > > > Deepak Shetty wrote: > > > >>It seems jmeter http cookie manager only keep one cookie per domain. > > Not true. > > What do the two set-cookies look like? Note that there are domain and > path > > parameters that can be set which influence whether or not jmeter will > send > > the cookie with the request > > > > regards > > deepak > > > > On Wed, Nov 18, 2009 at 9:49 AM, Chester Chee wrote: > > > >> > >> Hi, > >> > >> I am using JMeter 2.3.4 on Ubuntu 9.10 hitting a web server with web > apps > >> that uses two phases authentication. To complete the authentication, two > >> cookies from the website (same domain) must to presented in the GET > >> request > >> to the server. > >> > >> I had debug enabled for HTTP Cookie Manager and based on the information > >> presented in jmeter.log, I know for sure that the server did send two > >> Set-Cookie: with different cookie names back in its responses. And the > >> jmeter log indicate both are received and store. But only one is found > >> when > >> look up and that was the last one being sent. > >> > >> It seems jmeter http cookie manager only keep one cookie per domain. > >> > >> Is this true? If so, I don't think this the case with normal browser > >> nowadays. Is there a workaround for this? May be configuration parameter > >> i > >> can specified to overcome this in jmeter.properties? Or this is a bug? > >> Anyone experience the similar issue? > >> > >> Your kind attention and prompt responses are very much appreciated. > >> Thanks > >> in advance. > >> > >> Regards, > >> Chester > >> -- > >> View this message in context: > >> http://old.nabble.com/JMeter-Cookie-Manager-tp26412473p26412473.html > >> Sent from the JMeter - User mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >> > >> > > > > > > -- > View this message in context: > http://old.nabble.com/Re%3A-JMeter-Cookie-Manager-tp26415243p26416606.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
Re: JMeter Cookie Manager
Both have the same domain and path, but different url and name. For example, SID (session id) from url /cgi-bin/login XX_AT (authentication token) from url /cgi-bin/pin Deepak Shetty wrote: > >>It seems jmeter http cookie manager only keep one cookie per domain. > Not true. > What do the two set-cookies look like? Note that there are domain and path > parameters that can be set which influence whether or not jmeter will send > the cookie with the request > > regards > deepak > > On Wed, Nov 18, 2009 at 9:49 AM, Chester Chee wrote: > >> >> Hi, >> >> I am using JMeter 2.3.4 on Ubuntu 9.10 hitting a web server with web apps >> that uses two phases authentication. To complete the authentication, two >> cookies from the website (same domain) must to presented in the GET >> request >> to the server. >> >> I had debug enabled for HTTP Cookie Manager and based on the information >> presented in jmeter.log, I know for sure that the server did send two >> Set-Cookie: with different cookie names back in its responses. And the >> jmeter log indicate both are received and store. But only one is found >> when >> look up and that was the last one being sent. >> >> It seems jmeter http cookie manager only keep one cookie per domain. >> >> Is this true? If so, I don't think this the case with normal browser >> nowadays. Is there a workaround for this? May be configuration parameter >> i >> can specified to overcome this in jmeter.properties? Or this is a bug? >> Anyone experience the similar issue? >> >> Your kind attention and prompt responses are very much appreciated. >> Thanks >> in advance. >> >> Regards, >> Chester >> -- >> View this message in context: >> http://old.nabble.com/JMeter-Cookie-Manager-tp26412473p26412473.html >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> --------- >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> > > -- View this message in context: http://old.nabble.com/Re%3A-JMeter-Cookie-Manager-tp26415243p26416606.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: JMeter Cookie Manager
>It seems jmeter http cookie manager only keep one cookie per domain. Not true. What do the two set-cookies look like? Note that there are domain and path parameters that can be set which influence whether or not jmeter will send the cookie with the request regards deepak On Wed, Nov 18, 2009 at 9:49 AM, Chester Chee wrote: > > Hi, > > I am using JMeter 2.3.4 on Ubuntu 9.10 hitting a web server with web apps > that uses two phases authentication. To complete the authentication, two > cookies from the website (same domain) must to presented in the GET request > to the server. > > I had debug enabled for HTTP Cookie Manager and based on the information > presented in jmeter.log, I know for sure that the server did send two > Set-Cookie: with different cookie names back in its responses. And the > jmeter log indicate both are received and store. But only one is found when > look up and that was the last one being sent. > > It seems jmeter http cookie manager only keep one cookie per domain. > > Is this true? If so, I don't think this the case with normal browser > nowadays. Is there a workaround for this? May be configuration parameter i > can specified to overcome this in jmeter.properties? Or this is a bug? > Anyone experience the similar issue? > > Your kind attention and prompt responses are very much appreciated. Thanks > in advance. > > Regards, > Chester > -- > View this message in context: > http://old.nabble.com/JMeter-Cookie-Manager-tp26412473p26412473.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
JMeter HTTP Cookie Manager
Hi, I am using JMeter 2.3.4 on Ubuntu 9.10 hitting a web server with web apps that uses two phases authentication. To complete the authentication, two cookies from the website (same domain) must to presented in the GET request to the server. I had debug enabled for HTTP Cookie Manager and based on the information presented in jmeter.log, I know for sure that the server did send two Set-Cookie: with different cookie names back in its responses. And the jmeter log indicate both are received and store. But only one is found when look up and that was the last one being sent. It seems jmeter http cookie manager only keep one cookie per domain. Is this true? If so, I don't think this the case with normal browser nowadays. Is there a workaround for this? May be configuration parameter i can specified to overcome this in jmeter.properties? Or this is a bug? Anyone experience the similar issue? Your kind attention and prompt responses are very much appreciated. Thanks in advance. -- View this message in context: http://old.nabble.com/JMeter-HTTP-Cookie-Manager-tp26412685p26412685.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
JMeter Cookie Manager
Hi, I am using JMeter 2.3.4 on Ubuntu 9.10 hitting a web server with web apps that uses two phases authentication. To complete the authentication, two cookies from the website (same domain) must to presented in the GET request to the server. I had debug enabled for HTTP Cookie Manager and based on the information presented in jmeter.log, I know for sure that the server did send two Set-Cookie: with different cookie names back in its responses. And the jmeter log indicate both are received and store. But only one is found when look up and that was the last one being sent. It seems jmeter http cookie manager only keep one cookie per domain. Is this true? If so, I don't think this the case with normal browser nowadays. Is there a workaround for this? May be configuration parameter i can specified to overcome this in jmeter.properties? Or this is a bug? Anyone experience the similar issue? Your kind attention and prompt responses are very much appreciated. Thanks in advance. Regards, Chester -- View this message in context: http://old.nabble.com/JMeter-Cookie-Manager-tp26412473p26412473.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
RE: Cookie Manager
Yes, I realized that was what was happening AFTER I posted. -a -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Thursday, June 18, 2009 12:02 PM To: JMeter Users List Subject: Re: Cookie Manager Also make sure that the browser does not already have a cookie from an existing session. On 18/06/2009, Deepak Shetty wrote: > Hi > the sample you have posted isnt the same as for the one in your earlier > emails (here you already have a session and no login request , earlier you > had a login request). You will have to record what your browser gets (using > livehttpheaders) and when running jmeter, enable View results tree and > compare each request with what LiveHttpHeaders shows. You may have missed > some posted data or variable or something > I dont think the HTTPManager's cookie policy is causing your problem but I > assume its using compatibility? > regards > deepak > > On Thu, Jun 18, 2009 at 4:50 AM, Stromas, Aaron (NIH/OD) [C] < > > stroma...@od.nih.gov> wrote: > > > > Hi, > > > > Yes, the site works. Thanks for explaining and the tip about Live HTTP > > Headers. I see now that it is the browser that sends the cookie (see > below). > > I haven't expected that at all! And I can also see that the returned cookie > > is for the correct path. > > > > On the other hand, WRT my previous attempt to use the HTTP Proxy, it > > seemingly detected SSL, but there is no trace of the SSL at all. Thanks > > again for your help. > > > > -a > > > > > > > http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10 > > > > > > GET /eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10 > > HTTP/1.1 > > Host: webappdev4.era.nih.gov:7783 > > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) > > Gecko/2009060215 Firefox/3.0.11 (.NET CLR 3.5.30729) > > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > > Accept-Language: en-us,en;q=0.5 > > Accept-Encoding: gzip,deflate > > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > > Keep-Alive: 300 > > Connection: keep-alive > > Cookie: > > > JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe; > > newuser=stromasam; > > > SSO_ID=v1.2~1~A68A68203646B8461E64EBD38FAB71907100F8EDC78A2CD0EF123B6DADF5DE9AA7638F731C97EA400FC7662DED49B00EF6C862C3E55734670C76A5681B559060F8470AFB497C9159811D4579921FC20C5A2A85C7CF1493C8A7FB2943D83DC798FB0A0F917553BF7C6742D70E4F2046777DF13CAA07F1AA8A94497EFC809E737B16496EC81E43B292630E49CF723F24760F83F1F950063B603A33EE874E3041962AB8A139266B4C45CBA0C7A8ED05928A8EDE0B15EC24C3F27A594A787C0B8D3DE6D903C7D50976CFBB8388B4341CFCE4BCB3E345A2584AAC1F20A6986416D18F37E8A56F874AE264BBC9EABD7C5F0D1297179398CEB259A774ECF9B3F9E4 > > > > > > > > HTTP/1.x 302 Redirect to Oracle SSO Server > > Date: Thu, 18 Jun 2009 11:20:25 GMT > > Server: Oracle-Application-Server-10g/10.1.2.0.2 Oracle-HTTP-Server > > Location: > > > http://webappdev4.era.nih.gov:7781/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=v1.4~D3D5AF18~641295BAA8EBB4765B3FA739FA32E8FDA7E7BCA2AA992083E1A94553B90D816486AC26729EA2569E64E71AC6016DE94C85FC21336DB3B7F0A17EA58F5B6E0CE916EF73738F618A064515BF0410CD2FE14AF14E474ABC090BA23908B952DFD5258FDE04EB99DB87C47C66F2ED30DD225F2BDD54037FFA0795553642636AB07728FA25B0D998C0DA26A550ACD2D9F7B604906257D7AA1AFAA75DF9A2F14709E20CB310F32EE6CAC556B7A276A868E221C792A229198D84C0D037D9850DC77B4728091CDB338220841046BB64873A8F01635552FDF6E794BEC512F197D0325F6BE2FAF0C2CFED24985D2812CABC8EF220C36388C7F1956E354CE067BAA15EC092C41DF40289D8D8E98CA376BAB381F330BA > > > Set-Cookie<http://webappdev4.era.nih.gov:7781/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=v1.4%7ED3D5AF18%7E641295BAA8EBB4765B3FA739FA32E8FDA7E7BCA2AA992083E1A94553B90D816486AC26729EA2569E64E71AC6016DE94C85FC21336DB3B7F0A17EA58F5B6E0CE916EF73738F618A064515BF0410CD2FE14AF14E474ABC090BA23908B952DFD5258FDE04EB99DB87C47C66F2ED30DD225F2BDD54037FFA0795553642636AB07728FA25B0D998C0DA26A550ACD2D9F7B604906257D7AA1AFAA75DF9A2F14709E20CB310F32EE6CAC556B7A276A868E221C792A229198D84C0D037D9850DC77B4728091CDB338220841046BB64873A8F01635552FDF6E794BEC512F197D0325F6BE2FAF0C2CFED24985D2812CABC8EF220C36388C7F1956E354CE067BAA15EC092C41DF40289D8D8E98CA376BAB381F330BA%0ASet-Cookie>: > > > JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe; > > path=/eraservices > > Cache-Control: private > > Osso-Paranoid: false > > Keep-Alive: timeout=15, max=100 > >
RE: Cookie Manager
Yes, livehttpheaders helps a great deal. Firebug did not show all the requests, so I wasn't coding the test plan correctly. There are several redirections (3XX) that livehttpheaders captured, but the Firebug did show. You are correct, the Cookie Manager works fine. -a -Original Message- From: Deepak Shetty [mailto:shet...@gmail.com] Sent: Thursday, June 18, 2009 11:58 AM To: JMeter Users List Subject: Re: Cookie Manager Hi the sample you have posted isnt the same as for the one in your earlier emails (here you already have a session and no login request , earlier you had a login request). You will have to record what your browser gets (using livehttpheaders) and when running jmeter, enable View results tree and compare each request with what LiveHttpHeaders shows. You may have missed some posted data or variable or something I dont think the HTTPManager's cookie policy is causing your problem but I assume its using compatibility? regards deepak On Thu, Jun 18, 2009 at 4:50 AM, Stromas, Aaron (NIH/OD) [C] < stroma...@od.nih.gov> wrote: > Hi, > > Yes, the site works. Thanks for explaining and the tip about Live HTTP > Headers. I see now that it is the browser that sends the cookie (see below). > I haven't expected that at all! And I can also see that the returned cookie > is for the correct path. > > On the other hand, WRT my previous attempt to use the HTTP Proxy, it > seemingly detected SSL, but there is no trace of the SSL at all. Thanks > again for your help. > > -a > > > http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10 > > > GET /eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10 > HTTP/1.1 > Host: webappdev4.era.nih.gov:7783 > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) > Gecko/2009060215 Firefox/3.0.11 (.NET CLR 3.5.30729) > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: en-us,en;q=0.5 > Accept-Encoding: gzip,deflate > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > Keep-Alive: 300 > Connection: keep-alive > Cookie: > JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe; > newuser=stromasam; > SSO_ID=v1.2~1~A68A68203646B8461E64EBD38FAB71907100F8EDC78A2CD0EF123B6DADF5DE9AA7638F731C97EA400FC7662DED49B00EF6C862C3E55734670C76A5681B559060F8470AFB497C9159811D4579921FC20C5A2A85C7CF1493C8A7FB2943D83DC798FB0A0F917553BF7C6742D70E4F2046777DF13CAA07F1AA8A94497EFC809E737B16496EC81E43B292630E49CF723F24760F83F1F950063B603A33EE874E3041962AB8A139266B4C45CBA0C7A8ED05928A8EDE0B15EC24C3F27A594A787C0B8D3DE6D903C7D50976CFBB8388B4341CFCE4BCB3E345A2584AAC1F20A6986416D18F37E8A56F874AE264BBC9EABD7C5F0D1297179398CEB259A774ECF9B3F9E4 > > > > HTTP/1.x 302 Redirect to Oracle SSO Server > Date: Thu, 18 Jun 2009 11:20:25 GMT > Server: Oracle-Application-Server-10g/10.1.2.0.2 Oracle-HTTP-Server > Location: > http://webappdev4.era.nih.gov:7781/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=v1.4~D3D5AF18~641295BAA8EBB4765B3FA739FA32E8FDA7E7BCA2AA992083E1A94553B90D816486AC26729EA2569E64E71AC6016DE94C85FC21336DB3B7F0A17EA58F5B6E0CE916EF73738F618A064515BF0410CD2FE14AF14E474ABC090BA23908B952DFD5258FDE04EB99DB87C47C66F2ED30DD225F2BDD54037FFA0795553642636AB07728FA25B0D998C0DA26A550ACD2D9F7B604906257D7AA1AFAA75DF9A2F14709E20CB310F32EE6CAC556B7A276A868E221C792A229198D84C0D037D9850DC77B4728091CDB338220841046BB64873A8F01635552FDF6E794BEC512F197D0325F6BE2FAF0C2CFED24985D2812CABC8EF220C36388C7F1956E354CE067BAA15EC092C41DF40289D8D8E98CA376BAB381F330BA > Set-Cookie<http://webappdev4.era.nih.gov:7781/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=v1.4%7ED3D5AF18%7E641295BAA8EBB4765B3FA739FA32E8FDA7E7BCA2AA992083E1A94553B90D816486AC26729EA2569E64E71AC6016DE94C85FC21336DB3B7F0A17EA58F5B6E0CE916EF73738F618A064515BF0410CD2FE14AF14E474ABC090BA23908B952DFD5258FDE04EB99DB87C47C66F2ED30DD225F2BDD54037FFA0795553642636AB07728FA25B0D998C0DA26A550ACD2D9F7B604906257D7AA1AFAA75DF9A2F14709E20CB310F32EE6CAC556B7A276A868E221C792A229198D84C0D037D9850DC77B4728091CDB338220841046BB64873A8F01635552FDF6E794BEC512F197D0325F6BE2FAF0C2CFED24985D2812CABC8EF220C36388C7F1956E354CE067BAA15EC092C41DF40289D8D8E98CA376BAB381F330BA%0ASet-Cookie>: > JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe; > path=/eraservices > Cache-Control: private > Osso-Paranoid: false > Keep-Alive: timeout=15, max=100 > Connection: Keep-Alive > Transfer-Encoding: chunked > Content-Type: text/html > > > -Original Message- > From: Deepak Shetty [mailto:shet...@gmail.com] > Sent: Wednesday, June 17, 2009 3:37 PM > To: JMeter Users List > Subject: Re: Cookie Manager > > Hi > this i
Re: Cookie Manager
Also make sure that the browser does not already have a cookie from an existing session. On 18/06/2009, Deepak Shetty wrote: > Hi > the sample you have posted isnt the same as for the one in your earlier > emails (here you already have a session and no login request , earlier you > had a login request). You will have to record what your browser gets (using > livehttpheaders) and when running jmeter, enable View results tree and > compare each request with what LiveHttpHeaders shows. You may have missed > some posted data or variable or something > I dont think the HTTPManager's cookie policy is causing your problem but I > assume its using compatibility? > regards > deepak > > On Thu, Jun 18, 2009 at 4:50 AM, Stromas, Aaron (NIH/OD) [C] < > > stroma...@od.nih.gov> wrote: > > > > Hi, > > > > Yes, the site works. Thanks for explaining and the tip about Live HTTP > > Headers. I see now that it is the browser that sends the cookie (see > below). > > I haven't expected that at all! And I can also see that the returned cookie > > is for the correct path. > > > > On the other hand, WRT my previous attempt to use the HTTP Proxy, it > > seemingly detected SSL, but there is no trace of the SSL at all. Thanks > > again for your help. > > > > -a > > > > > > > http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10 > > > > > > GET /eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10 > > HTTP/1.1 > > Host: webappdev4.era.nih.gov:7783 > > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) > > Gecko/2009060215 Firefox/3.0.11 (.NET CLR 3.5.30729) > > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > > Accept-Language: en-us,en;q=0.5 > > Accept-Encoding: gzip,deflate > > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > > Keep-Alive: 300 > > Connection: keep-alive > > Cookie: > > > JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe; > > newuser=stromasam; > > > SSO_ID=v1.2~1~A68A68203646B8461E64EBD38FAB71907100F8EDC78A2CD0EF123B6DADF5DE9AA7638F731C97EA400FC7662DED49B00EF6C862C3E55734670C76A5681B559060F8470AFB497C9159811D4579921FC20C5A2A85C7CF1493C8A7FB2943D83DC798FB0A0F917553BF7C6742D70E4F2046777DF13CAA07F1AA8A94497EFC809E737B16496EC81E43B292630E49CF723F24760F83F1F950063B603A33EE874E3041962AB8A139266B4C45CBA0C7A8ED05928A8EDE0B15EC24C3F27A594A787C0B8D3DE6D903C7D50976CFBB8388B4341CFCE4BCB3E345A2584AAC1F20A6986416D18F37E8A56F874AE264BBC9EABD7C5F0D1297179398CEB259A774ECF9B3F9E4 > > > > > > > > HTTP/1.x 302 Redirect to Oracle SSO Server > > Date: Thu, 18 Jun 2009 11:20:25 GMT > > Server: Oracle-Application-Server-10g/10.1.2.0.2 Oracle-HTTP-Server > > Location: > > > http://webappdev4.era.nih.gov:7781/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=v1.4~D3D5AF18~641295BAA8EBB4765B3FA739FA32E8FDA7E7BCA2AA992083E1A94553B90D816486AC26729EA2569E64E71AC6016DE94C85FC21336DB3B7F0A17EA58F5B6E0CE916EF73738F618A064515BF0410CD2FE14AF14E474ABC090BA23908B952DFD5258FDE04EB99DB87C47C66F2ED30DD225F2BDD54037FFA0795553642636AB07728FA25B0D998C0DA26A550ACD2D9F7B604906257D7AA1AFAA75DF9A2F14709E20CB310F32EE6CAC556B7A276A868E221C792A229198D84C0D037D9850DC77B4728091CDB338220841046BB64873A8F01635552FDF6E794BEC512F197D0325F6BE2FAF0C2CFED24985D2812CABC8EF220C36388C7F1956E354CE067BAA15EC092C41DF40289D8D8E98CA376BAB381F330BA > > > Set-Cookie<http://webappdev4.era.nih.gov:7781/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=v1.4%7ED3D5AF18%7E641295BAA8EBB4765B3FA739FA32E8FDA7E7BCA2AA992083E1A94553B90D816486AC26729EA2569E64E71AC6016DE94C85FC21336DB3B7F0A17EA58F5B6E0CE916EF73738F618A064515BF0410CD2FE14AF14E474ABC090BA23908B952DFD5258FDE04EB99DB87C47C66F2ED30DD225F2BDD54037FFA0795553642636AB07728FA25B0D998C0DA26A550ACD2D9F7B604906257D7AA1AFAA75DF9A2F14709E20CB310F32EE6CAC556B7A276A868E221C792A229198D84C0D037D9850DC77B4728091CDB338220841046BB64873A8F01635552FDF6E794BEC512F197D0325F6BE2FAF0C2CFED24985D2812CABC8EF220C36388C7F1956E354CE067BAA15EC092C41DF40289D8D8E98CA376BAB381F330BA%0ASet-Cookie>: > > > JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe; > > path=/eraservices > > Cache-Control: private > > Osso-Paranoid: false > > Keep-Alive: timeout=15, max=100 > > Connection: Keep-Alive > > Transfer-Encoding: chunked > > Content-Type: text/html > > > > > > -Original Message- > > From: Deepak Shetty [mailto:shet...@gmail.com] >
Re: Cookie Manager
Hi the sample you have posted isnt the same as for the one in your earlier emails (here you already have a session and no login request , earlier you had a login request). You will have to record what your browser gets (using livehttpheaders) and when running jmeter, enable View results tree and compare each request with what LiveHttpHeaders shows. You may have missed some posted data or variable or something I dont think the HTTPManager's cookie policy is causing your problem but I assume its using compatibility? regards deepak On Thu, Jun 18, 2009 at 4:50 AM, Stromas, Aaron (NIH/OD) [C] < stroma...@od.nih.gov> wrote: > Hi, > > Yes, the site works. Thanks for explaining and the tip about Live HTTP > Headers. I see now that it is the browser that sends the cookie (see below). > I haven't expected that at all! And I can also see that the returned cookie > is for the correct path. > > On the other hand, WRT my previous attempt to use the HTTP Proxy, it > seemingly detected SSL, but there is no trace of the SSL at all. Thanks > again for your help. > > -a > > > http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10 > > > GET /eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10 > HTTP/1.1 > Host: webappdev4.era.nih.gov:7783 > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) > Gecko/2009060215 Firefox/3.0.11 (.NET CLR 3.5.30729) > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: en-us,en;q=0.5 > Accept-Encoding: gzip,deflate > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > Keep-Alive: 300 > Connection: keep-alive > Cookie: > JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe; > newuser=stromasam; > SSO_ID=v1.2~1~A68A68203646B8461E64EBD38FAB71907100F8EDC78A2CD0EF123B6DADF5DE9AA7638F731C97EA400FC7662DED49B00EF6C862C3E55734670C76A5681B559060F8470AFB497C9159811D4579921FC20C5A2A85C7CF1493C8A7FB2943D83DC798FB0A0F917553BF7C6742D70E4F2046777DF13CAA07F1AA8A94497EFC809E737B16496EC81E43B292630E49CF723F24760F83F1F950063B603A33EE874E3041962AB8A139266B4C45CBA0C7A8ED05928A8EDE0B15EC24C3F27A594A787C0B8D3DE6D903C7D50976CFBB8388B4341CFCE4BCB3E345A2584AAC1F20A6986416D18F37E8A56F874AE264BBC9EABD7C5F0D1297179398CEB259A774ECF9B3F9E4 > > > > HTTP/1.x 302 Redirect to Oracle SSO Server > Date: Thu, 18 Jun 2009 11:20:25 GMT > Server: Oracle-Application-Server-10g/10.1.2.0.2 Oracle-HTTP-Server > Location: > http://webappdev4.era.nih.gov:7781/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=v1.4~D3D5AF18~641295BAA8EBB4765B3FA739FA32E8FDA7E7BCA2AA992083E1A94553B90D816486AC26729EA2569E64E71AC6016DE94C85FC21336DB3B7F0A17EA58F5B6E0CE916EF73738F618A064515BF0410CD2FE14AF14E474ABC090BA23908B952DFD5258FDE04EB99DB87C47C66F2ED30DD225F2BDD54037FFA0795553642636AB07728FA25B0D998C0DA26A550ACD2D9F7B604906257D7AA1AFAA75DF9A2F14709E20CB310F32EE6CAC556B7A276A868E221C792A229198D84C0D037D9850DC77B4728091CDB338220841046BB64873A8F01635552FDF6E794BEC512F197D0325F6BE2FAF0C2CFED24985D2812CABC8EF220C36388C7F1956E354CE067BAA15EC092C41DF40289D8D8E98CA376BAB381F330BA > Set-Cookie<http://webappdev4.era.nih.gov:7781/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=v1.4%7ED3D5AF18%7E641295BAA8EBB4765B3FA739FA32E8FDA7E7BCA2AA992083E1A94553B90D816486AC26729EA2569E64E71AC6016DE94C85FC21336DB3B7F0A17EA58F5B6E0CE916EF73738F618A064515BF0410CD2FE14AF14E474ABC090BA23908B952DFD5258FDE04EB99DB87C47C66F2ED30DD225F2BDD54037FFA0795553642636AB07728FA25B0D998C0DA26A550ACD2D9F7B604906257D7AA1AFAA75DF9A2F14709E20CB310F32EE6CAC556B7A276A868E221C792A229198D84C0D037D9850DC77B4728091CDB338220841046BB64873A8F01635552FDF6E794BEC512F197D0325F6BE2FAF0C2CFED24985D2812CABC8EF220C36388C7F1956E354CE067BAA15EC092C41DF40289D8D8E98CA376BAB381F330BA%0ASet-Cookie>: > JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe; > path=/eraservices > Cache-Control: private > Osso-Paranoid: false > Keep-Alive: timeout=15, max=100 > Connection: Keep-Alive > Transfer-Encoding: chunked > Content-Type: text/html > > > -Original Message- > From: Deepak Shetty [mailto:shet...@gmail.com] > Sent: Wednesday, June 17, 2009 3:37 PM > To: JMeter Users List > Subject: Re: Cookie Manager > > Hi > this is correct behavior, you cant specify a different path for Set-Cookie > than the path value you are requesting for(or parents of the path). Does > this site work when you access it using a browser(use firefox plus > livehttpheaders)? If so can you compare what you are getting in Set-Cookie > (the path, domain) when you access it via the browser. > This looks to be a server problem, JSESSIONID should always have a path as > '/'
RE: Cookie Manager
Hi,
Yes, the site works. Thanks for explaining and the tip about Live HTTP Headers.
I see now that it is the browser that sends the cookie (see below). I haven't
expected that at all! And I can also see that the returned cookie is for the
correct path.
On the other hand, WRT my previous attempt to use the HTTP Proxy, it seemingly
detected SSL, but there is no trace of the SSL at all. Thanks again for your
help.
-a
http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10
GET /eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10
HTTP/1.1
Host: webappdev4.era.nih.gov:7783
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11)
Gecko/2009060215 Firefox/3.0.11 (.NET CLR 3.5.30729)
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie:
JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe;
newuser=stromasam;
SSO_ID=v1.2~1~A68A68203646B8461E64EBD38FAB71907100F8EDC78A2CD0EF123B6DADF5DE9AA7638F731C97EA400FC7662DED49B00EF6C862C3E55734670C76A5681B559060F8470AFB497C9159811D4579921FC20C5A2A85C7CF1493C8A7FB2943D83DC798FB0A0F917553BF7C6742D70E4F2046777DF13CAA07F1AA8A94497EFC809E737B16496EC81E43B292630E49CF723F24760F83F1F950063B603A33EE874E3041962AB8A139266B4C45CBA0C7A8ED05928A8EDE0B15EC24C3F27A594A787C0B8D3DE6D903C7D50976CFBB8388B4341CFCE4BCB3E345A2584AAC1F20A6986416D18F37E8A56F874AE264BBC9EABD7C5F0D1297179398CEB259A774ECF9B3F9E4
HTTP/1.x 302 Redirect to Oracle SSO Server
Date: Thu, 18 Jun 2009 11:20:25 GMT
Server: Oracle-Application-Server-10g/10.1.2.0.2 Oracle-HTTP-Server
Location:
http://webappdev4.era.nih.gov:7781/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=v1.4~D3D5AF18~641295BAA8EBB4765B3FA739FA32E8FDA7E7BCA2AA992083E1A94553B90D816486AC26729EA2569E64E71AC6016DE94C85FC21336DB3B7F0A17EA58F5B6E0CE916EF73738F618A064515BF0410CD2FE14AF14E474ABC090BA23908B952DFD5258FDE04EB99DB87C47C66F2ED30DD225F2BDD54037FFA0795553642636AB07728FA25B0D998C0DA26A550ACD2D9F7B604906257D7AA1AFAA75DF9A2F14709E20CB310F32EE6CAC556B7A276A868E221C792A229198D84C0D037D9850DC77B4728091CDB338220841046BB64873A8F01635552FDF6E794BEC512F197D0325F6BE2FAF0C2CFED24985D2812CABC8EF220C36388C7F1956E354CE067BAA15EC092C41DF40289D8D8E98CA376BAB381F330BA
Set-Cookie:
JSESSIONID=9c28ee1630d6c16635be49ee9029b88b9f91b59c.e3yLaxaTbx0Qe34KaxaSbxyLaNz0n6jAmljGr5XDqQLvpAe;
path=/eraservices
Cache-Control: private
Osso-Paranoid: false
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html
-Original Message-
From: Deepak Shetty [mailto:shet...@gmail.com]
Sent: Wednesday, June 17, 2009 3:37 PM
To: JMeter Users List
Subject: Re: Cookie Manager
Hi
this is correct behavior, you cant specify a different path for Set-Cookie
than the path value you are requesting for(or parents of the path). Does
this site work when you access it using a browser(use firefox plus
livehttpheaders)? If so can you compare what you are getting in Set-Cookie
(the path, domain) when you access it via the browser.
This looks to be a server problem, JSESSIONID should always have a path as
'/' unless you have multiple web-apps
regards
deepak
On Wed, Jun 17, 2009 at 12:05 PM, Stromas, Aaron (NIH/OD) [C] <
stroma...@od.nih.gov> wrote:
> Greetings again!
>
> The log shows that the cookie returned by the Oracle SSO server isn't
> stored by the Cookie Manager, which is a big problem. A show stopper, in
> fact. Can anyone help me with this? Here is what the log shows:
>
> 2009/06/17 14:44:08 DEBUG - jmeter.protocol.http.control.CookieManager:
> Received Cookie:
> JSESSIONID=9c28ee1630d506e961794696437da92ee6b5154398c0.e34PahuKc3eKby0QaxyMbNmRbNn0n6jAmljGr5XDqQLvpAe;
> path=/auth From:
> http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=${applID}&folderID=10<http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=$%7BapplID%7D&folderID=10>
> 2009/06/17 14:44:08 DEBUG - jmeter.protocol.http.control.CookieManager: Not
> storing invalid cookie:
> path=/auth> for URL
> http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=${applID}&folderID=10<http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=$%7BapplID%7D&folderID=10>(Illegal
> path attribute "/auth". Path of origin:
> "/eraservices/grantfolder/viewGrantFolder.do")
> 2009/06/17 14:44:08 DEBUG - jmeter.protocol.http.control.CookieManager:
> Found 0 cookies for
> http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=${applID}&folderID=10<http://webapp
Re: Cookie Manager
Hi
this is correct behavior, you cant specify a different path for Set-Cookie
than the path value you are requesting for(or parents of the path). Does
this site work when you access it using a browser(use firefox plus
livehttpheaders)? If so can you compare what you are getting in Set-Cookie
(the path, domain) when you access it via the browser.
This looks to be a server problem, JSESSIONID should always have a path as
'/' unless you have multiple web-apps
regards
deepak
On Wed, Jun 17, 2009 at 12:05 PM, Stromas, Aaron (NIH/OD) [C] <
stroma...@od.nih.gov> wrote:
> Greetings again!
>
> The log shows that the cookie returned by the Oracle SSO server isn't
> stored by the Cookie Manager, which is a big problem. A show stopper, in
> fact. Can anyone help me with this? Here is what the log shows:
>
> 2009/06/17 14:44:08 DEBUG - jmeter.protocol.http.control.CookieManager:
> Received Cookie:
> JSESSIONID=9c28ee1630d506e961794696437da92ee6b5154398c0.e34PahuKc3eKby0QaxyMbNmRbNn0n6jAmljGr5XDqQLvpAe;
> path=/auth From:
> http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=${applID}&folderID=10<http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=$%7BapplID%7D&folderID=10>
> 2009/06/17 14:44:08 DEBUG - jmeter.protocol.http.control.CookieManager: Not
> storing invalid cookie:
> path=/auth> for URL
> http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=${applID}&folderID=10<http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=$%7BapplID%7D&folderID=10>(Illegal
> path attribute "/auth". Path of origin:
> "/eraservices/grantfolder/viewGrantFolder.do")
> 2009/06/17 14:44:08 DEBUG - jmeter.protocol.http.control.CookieManager:
> Found 0 cookies for
> http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=${applID}&folderID=10<http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=$%7BapplID%7D&folderID=10>
>
> -Original Message-
> From: Stromas, Aaron (NIH/OD) [C]
> Sent: Wednesday, June 17, 2009 1:31 PM
> To: 'JMeter Users List'
> Subject: RE: Cookie Manager
>
> Hello again!
>
> I have turned on debugging for the Cookie Manager:
>
> 2009/06/17 13:19:41 DEBUG - jmeter.protocol.http.control.CookieManager:
> Received Cookie:
> JSESSIONID=9c28ee1630d5e880e94040eb42d49fb8bf6210325a77.e34PahuKc3eKby0QaxyMbNmRbNn0n6jAmljGr5XDqQLvpAe;
> path=/auth From: http://webappdev4.era.nih.gov:7781/auth/login.jsp
> 2009/06/17 13:19:41 DEBUG - jmeter.protocol.http.control.CookieManager: Add
> cookie to store webappdev4.era.nih.gov TRUE/auth FALSE 0
> JSESSIONID
>
> 9c28ee1630d5e880e94040eb42d49fb8bf6210325a77.e34PahuKc3eKby0QaxyMbNmRbNn0n6jAmljGr5XDqQLvpAe
> 2009/06/17 13:19:41 DEBUG - jmeter.protocol.http.control.CookieManager:
> Found 0 cookies for
> http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10
>
>
> If I'm reading this correctly, the cookie isn't used for the second request
> because it is associated with a different URL. Is there a way to associate
> the returned cookie with /eraservices/grantfolde/viewGrantFolder.do?
>
> -a
>
> -Original Message-
> From: Noel O'Brien [mailto:nobr...@newbay.com]
> Sent: Wednesday, June 17, 2009 11:45 AM
> To: JMeter Users List
> Subject: Re: Cookie Manager
>
> Whereabouts in the test plan have you added the Cookie Manager?
>
> See
> http://jakarta.apache.org/jmeter/usermanual/build-web-test-plan.html#adding_cookie_supportfor
> more info.
>
> Regards,
> Noel
>
> - "Aaron Stromas (NIH/OD) [C]" wrote:
> > Hello again,
> >
> > I have added a Cookie Manager to my hand coded test plan. The first
> response sets a cookie: Set-Cookie: JSESSIONID= but the next request has
> no cookies ([no cookies] under the Response data tab. What am I doing wrong?
> TIA
> >
> > -a
> >
>
> --
> Regards,
> Noel
>
> -
> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
>
>
RE: Cookie Manager
Greetings again!
The log shows that the cookie returned by the Oracle SSO server isn't stored by
the Cookie Manager, which is a big problem. A show stopper, in fact. Can anyone
help me with this? Here is what the log shows:
2009/06/17 14:44:08 DEBUG - jmeter.protocol.http.control.CookieManager:
Received Cookie:
JSESSIONID=9c28ee1630d506e961794696437da92ee6b5154398c0.e34PahuKc3eKby0QaxyMbNmRbNn0n6jAmljGr5XDqQLvpAe;
path=/auth From:
http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=${applID}&folderID=10
2009/06/17 14:44:08 DEBUG - jmeter.protocol.http.control.CookieManager: Not
storing invalid cookie:
for URL
http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=${applID}&folderID=10
(Illegal path attribute "/auth". Path of origin:
"/eraservices/grantfolder/viewGrantFolder.do")
2009/06/17 14:44:08 DEBUG - jmeter.protocol.http.control.CookieManager: Found 0
cookies for
http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=${applID}&folderID=10
-Original Message-
From: Stromas, Aaron (NIH/OD) [C]
Sent: Wednesday, June 17, 2009 1:31 PM
To: 'JMeter Users List'
Subject: RE: Cookie Manager
Hello again!
I have turned on debugging for the Cookie Manager:
2009/06/17 13:19:41 DEBUG - jmeter.protocol.http.control.CookieManager:
Received Cookie:
JSESSIONID=9c28ee1630d5e880e94040eb42d49fb8bf6210325a77.e34PahuKc3eKby0QaxyMbNmRbNn0n6jAmljGr5XDqQLvpAe;
path=/auth From: http://webappdev4.era.nih.gov:7781/auth/login.jsp
2009/06/17 13:19:41 DEBUG - jmeter.protocol.http.control.CookieManager: Add
cookie to store webappdev4.era.nih.gov TRUE/auth FALSE 0
JSESSIONID
9c28ee1630d5e880e94040eb42d49fb8bf6210325a77.e34PahuKc3eKby0QaxyMbNmRbNn0n6jAmljGr5XDqQLvpAe
2009/06/17 13:19:41 DEBUG - jmeter.protocol.http.control.CookieManager: Found 0
cookies for
http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10
If I'm reading this correctly, the cookie isn't used for the second request
because it is associated with a different URL. Is there a way to associate the
returned cookie with /eraservices/grantfolde/viewGrantFolder.do?
-a
-Original Message-
From: Noel O'Brien [mailto:nobr...@newbay.com]
Sent: Wednesday, June 17, 2009 11:45 AM
To: JMeter Users List
Subject: Re: Cookie Manager
Whereabouts in the test plan have you added the Cookie Manager?
See
http://jakarta.apache.org/jmeter/usermanual/build-web-test-plan.html#adding_cookie_support
for more info.
Regards,
Noel
- "Aaron Stromas (NIH/OD) [C]" wrote:
> Hello again,
>
> I have added a Cookie Manager to my hand coded test plan. The first response
> sets a cookie: Set-Cookie: JSESSIONID= but the next request has no
> cookies ([no cookies] under the Response data tab. What am I doing wrong? TIA
>
> -a
>
--
Regards,
Noel
-
To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
RE: Cookie Manager
Hello again! I have turned on debugging for the Cookie Manager: 2009/06/17 13:19:41 DEBUG - jmeter.protocol.http.control.CookieManager: Received Cookie: JSESSIONID=9c28ee1630d5e880e94040eb42d49fb8bf6210325a77.e34PahuKc3eKby0QaxyMbNmRbNn0n6jAmljGr5XDqQLvpAe; path=/auth From: http://webappdev4.era.nih.gov:7781/auth/login.jsp 2009/06/17 13:19:41 DEBUG - jmeter.protocol.http.control.CookieManager: Add cookie to store webappdev4.era.nih.gov TRUE/auth FALSE 0 JSESSIONID 9c28ee1630d5e880e94040eb42d49fb8bf6210325a77.e34PahuKc3eKby0QaxyMbNmRbNn0n6jAmljGr5XDqQLvpAe 2009/06/17 13:19:41 DEBUG - jmeter.protocol.http.control.CookieManager: Found 0 cookies for http://webappdev4.era.nih.gov:7783/eraservices/grantfolder/viewGrantFolder.do?applID=7321077&folderID=10 If I'm reading this correctly, the cookie isn't used for the second request because it is associated with a different URL. Is there a way to associate the returned cookie with /eraservices/grantfolde/viewGrantFolder.do? -a -Original Message- From: Noel O'Brien [mailto:nobr...@newbay.com] Sent: Wednesday, June 17, 2009 11:45 AM To: JMeter Users List Subject: Re: Cookie Manager Whereabouts in the test plan have you added the Cookie Manager? See http://jakarta.apache.org/jmeter/usermanual/build-web-test-plan.html#adding_cookie_support for more info. Regards, Noel - "Aaron Stromas (NIH/OD) [C]" wrote: > Hello again, > > I have added a Cookie Manager to my hand coded test plan. The first response > sets a cookie: Set-Cookie: JSESSIONID= but the next request has no > cookies ([no cookies] under the Response data tab. What am I doing wrong? TIA > > -a > -- Regards, Noel - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
RE: Cookie Manager
I added it to the Thread Group. Under the thread group I have Login Config Element, CSV Data Set Config and HTTP Cookie Manager, HTTP Request Defaults followed by two HTTP Requests. -a -Original Message- From: Noel O'Brien [mailto:nobr...@newbay.com] Sent: Wednesday, June 17, 2009 11:45 AM To: JMeter Users List Subject: Re: Cookie Manager Whereabouts in the test plan have you added the Cookie Manager? See http://jakarta.apache.org/jmeter/usermanual/build-web-test-plan.html#adding_cookie_support for more info. Regards, Noel - "Aaron Stromas (NIH/OD) [C]" wrote: > Hello again, > > I have added a Cookie Manager to my hand coded test plan. The first response > sets a cookie: Set-Cookie: JSESSIONID= but the next request has no > cookies ([no cookies] under the Response data tab. What am I doing wrong? TIA > > -a > -- Regards, Noel - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: Cookie Manager
Whereabouts in the test plan have you added the Cookie Manager? See http://jakarta.apache.org/jmeter/usermanual/build-web-test-plan.html#adding_cookie_support for more info. Regards, Noel - "Aaron Stromas (NIH/OD) [C]" wrote: > Hello again, > > I have added a Cookie Manager to my hand coded test plan. The first response > sets a cookie: Set-Cookie: JSESSIONID= but the next request has no > cookies ([no cookies] under the Response data tab. What am I doing wrong? TIA > > -a > -- Regards, Noel
Cookie Manager
Hello again, I have added a Cookie Manager to my hand coded test plan. The first response sets a cookie: Set-Cookie: JSESSIONID= but the next request has no cookies ([no cookies] under the Response data tab. What am I doing wrong? TIA -a
Re: parameterised login creates problem with HTTP cookie manager
On 11/06/2009, ankush jethi wrote: > Hello friends, > Since we know using HTTP cookie manager lets jmeter use same session for all > the threads. Not true, unless you are using JMeter 2.3.1 which had a bug: http://wiki.apache.org/jakarta-jmeter/CookieManagerBugIn231 > But we are supposed to parametrize our user login. When I do > this my scripts dont execute at all. It seems very unlikely that the samplers don't even run. What error message is there? > Perhaps the reason could be that since > its a different user login for every request the same sessionID is no more > valid. No idea what you mean by that. > Also when I remove HTTP cookie manager none of my requests are > processed as every request produces a login page since no cookies are being > saved. That is true. > Any suggestions how can we resolve this issue? Explain better what you did, what you expected to happen and what actually happened, and someone might be able to help you. > Regards > > > -- > Regards > Ankush Jethi > It Is Very Easy To Be Brave From A Safe Distance. > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
parameterised login creates problem with HTTP cookie manager
Hello friends, Since we know using HTTP cookie manager lets jmeter use same session for all the threads. But we are supposed to parametrize our user login. When I do this my scripts dont execute at all. Perhaps the reason could be that since its a different user login for every request the same sessionID is no more valid. Also when I remove HTTP cookie manager none of my requests are processed as every request produces a login page since no cookies are being saved. Any suggestions how can we resolve this issue? Regards -- Regards Ankush Jethi It Is Very Easy To Be Brave From A Safe Distance.
RE: Cookie Manager
Please let me know the next step after finding the set-cookie for PS_TOKEN in the response headers. Thanks & Regards Sengamalam Kannan Testing CoE Mobile: +91 99529 67005 Tel: +91 44 6615 2684 -Original Message- From: Himanshu Ghai [mailto:himanshug...@gmail.com] Sent: Friday, May 01, 2009 4:26 AM To: JMeter Users List Subject: Re: Cookie Manager Look at the requests which set the cookie in response headers. If you have automatic redirects, i am not sure but i faintly remember you might need to redirect yourself to set cookies in jmeter. First step is to find the requests which set the cookies ps-token andps_login..in browser response headers look for set-cookie Himanshu On Thu, Apr 30, 2009 at 5:51 AM, Kannan, Sengamalam wrote: > Sebb > I also work with Ranjitha in solving the below issue. Let me try to explain > you clearly what issue we are facing. > > When we record scenario using JMeter, the jmeter request and response headers > are same as the browser's. > > But when we run the script, headers doent have the PS_TOKEN and PS_LOGIN > cookie parameter and only the PSJSESSIONID is present. > > We don't know how to solve this as we have also added Cookie Manager and > tried with all the policy options available there (ex: compatibility, rfc.., > default, etc) but nothing worked. > > Do we need to configure something else? Please help us to solve this. > > Thanks & Regards > Sengamalam Kannan > Testing CoE > Mobile: +91 99529 67005 > Tel: +91 44 6615 2684 > > -Original Message- > From: Prakash, Ranjitha [mailto:ranjitha.prak...@aig.com] > Sent: Thursday, April 30, 2009 6:14 PM > To: JMeter Users List > Subject: RE: Cookie Manager > > The recorded request header is the same as the browser request header. > > > Thanks and Regards, > Ranjitha Prakash > Mob: 9884383831 > Off: 66152735 > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > -Original Message- > From: Prakash, Ranjitha [mailto:ranjitha.prak...@aig.com] > Sent: Thursday, April 30, 2009 5:51 PM > To: JMeter Users List > Subject: RE: Cookie Manager > > Given below is the request header > > Request Headers: > Connection: keep-alive > Host: 10.46.188.36:8080 > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; > InfoPath.1) > Accept-Language: en-us > Referer: http://10.46.188.36:8080/psp/HR880TST/?cmd=login > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > application/x-shockwave-flash, application/vnd.ms-excel, > application/vnd.ms-powerpoint, application/msword, */* > > Thanks and Regards, > Ranjitha Prakash > Mob: 9884383831 > Off: 66152735 > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > -Original Message- > From: sebb [mailto:seb...@gmail.com] > Sent: Thursday, April 30, 2009 5:40 PM > To: JMeter Users List > Subject: Re: Cookie Manager > > What about the Requests? > > And how do these differ from the requests made by a browser? > > On 30/04/2009, Prakash, Ranjitha wrote: >> These are the recorded script response headers in JMeter. But when we run >> the script Response Headers doesn't have the PS_TOKEN, PS_LOGIN etc. Note >> that we have also ncluded Cookie Manager. >> >> Response headers: >> HTTP/1.1 200 OK >> Date: Thu, 30 Apr 2009 11:25:04 GMT >> Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 >> 09:54:21 >> Content-Encoding: gzip >> Content-Length: 1853 >> Content-Type: text/html; CHARSET=UTF-8 >> Expires: Thu, 01 Dec 1994 16:00:00 GMT >> UsesPortalRelativeURL: true >> Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:04_GMT; path=/ >> PortalRegisteredURL: >> http://10.46.188.36:8080/psc/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL >> >> Response headers: >> HTTP/1.1 200 OK >> Date: Thu, 30 Apr 2009 11:25:03 GMT >> Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 >> 09:54:21 >> Content-Encoding: gzip >> Content-Length: 716 >> Content-Type: text/html; CHARSET=UTF-8 >> Expires: Thu, 01 Dec 1994 16:00:00 GMT >> Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ >> >> >> Response headers: >> HTTP/1.1 302 Moved Temporarily >> Date: Thu, 30 Apr 2009 11:25:00 GMT >> Location: >> http://10.46.188.36:8080/psp/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL >> Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 >> 09:54:21 >> Content-Type: text/html >> Expires: Thu, 01 Dec 1994 16:00:00 GMT >&g
Re: Cookie Manager
Look at the requests which set the cookie in response headers. If you have automatic redirects, i am not sure but i faintly remember you might need to redirect yourself to set cookies in jmeter. First step is to find the requests which set the cookies ps-token andps_login..in browser response headers look for set-cookie Himanshu On Thu, Apr 30, 2009 at 5:51 AM, Kannan, Sengamalam wrote: > Sebb > I also work with Ranjitha in solving the below issue. Let me try to explain > you clearly what issue we are facing. > > When we record scenario using JMeter, the jmeter request and response headers > are same as the browser's. > > But when we run the script, headers doent have the PS_TOKEN and PS_LOGIN > cookie parameter and only the PSJSESSIONID is present. > > We don't know how to solve this as we have also added Cookie Manager and > tried with all the policy options available there (ex: compatibility, rfc.., > default, etc) but nothing worked. > > Do we need to configure something else? Please help us to solve this. > > Thanks & Regards > Sengamalam Kannan > Testing CoE > Mobile: +91 99529 67005 > Tel: +91 44 6615 2684 > > -Original Message- > From: Prakash, Ranjitha [mailto:ranjitha.prak...@aig.com] > Sent: Thursday, April 30, 2009 6:14 PM > To: JMeter Users List > Subject: RE: Cookie Manager > > The recorded request header is the same as the browser request header. > > > Thanks and Regards, > Ranjitha Prakash > Mob: 9884383831 > Off: 66152735 > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > -Original Message- > From: Prakash, Ranjitha [mailto:ranjitha.prak...@aig.com] > Sent: Thursday, April 30, 2009 5:51 PM > To: JMeter Users List > Subject: RE: Cookie Manager > > Given below is the request header > > Request Headers: > Connection: keep-alive > Host: 10.46.188.36:8080 > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; > InfoPath.1) > Accept-Language: en-us > Referer: http://10.46.188.36:8080/psp/HR880TST/?cmd=login > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > application/x-shockwave-flash, application/vnd.ms-excel, > application/vnd.ms-powerpoint, application/msword, */* > > Thanks and Regards, > Ranjitha Prakash > Mob: 9884383831 > Off: 66152735 > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > -Original Message- > From: sebb [mailto:seb...@gmail.com] > Sent: Thursday, April 30, 2009 5:40 PM > To: JMeter Users List > Subject: Re: Cookie Manager > > What about the Requests? > > And how do these differ from the requests made by a browser? > > On 30/04/2009, Prakash, Ranjitha wrote: >> These are the recorded script response headers in JMeter. But when we run >> the script Response Headers doesn't have the PS_TOKEN, PS_LOGIN etc. Note >> that we have also ncluded Cookie Manager. >> >> Response headers: >> HTTP/1.1 200 OK >> Date: Thu, 30 Apr 2009 11:25:04 GMT >> Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 >> 09:54:21 >> Content-Encoding: gzip >> Content-Length: 1853 >> Content-Type: text/html; CHARSET=UTF-8 >> Expires: Thu, 01 Dec 1994 16:00:00 GMT >> UsesPortalRelativeURL: true >> Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:04_GMT; path=/ >> PortalRegisteredURL: >> http://10.46.188.36:8080/psc/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL >> >> Response headers: >> HTTP/1.1 200 OK >> Date: Thu, 30 Apr 2009 11:25:03 GMT >> Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 >> 09:54:21 >> Content-Encoding: gzip >> Content-Length: 716 >> Content-Type: text/html; CHARSET=UTF-8 >> Expires: Thu, 01 Dec 1994 16:00:00 GMT >> Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ >> >> >> Response headers: >> HTTP/1.1 302 Moved Temporarily >> Date: Thu, 30 Apr 2009 11:25:00 GMT >> Location: >> http://10.46.188.36:8080/psp/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL >> Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 >> 09:54:21 >> Content-Type: text/html >> Expires: Thu, 01 Dec 1994 16:00:00 GMT >> Transfer-Encoding: Chunked >> Set-Cookie: SignOnDefault=; expires=Thursday, 07-May-2009 11:25:03 GMT; >> path=/ >> Set-Cookie: >> PS_TOKEN=sAQDAgEBvAIsBABTaGRyAk4AfQg4AC4AMQAwABSDa0+u3FOdXwNMa2yUaydpOJJjBnAFAFNkYXRhZHicHYpBDoJAEAQLJBx9gV9gs4H1sEcTXT0BAROPvsSf8TgrO53pztT0D+hObdOYR0udS2Fh46m/Wbmxq09ld/oHs6/zKiv
RE: Cookie Manager
Sebb I also work with Ranjitha in solving the below issue. Let me try to explain you clearly what issue we are facing. When we record scenario using JMeter, the jmeter request and response headers are same as the browser's. But when we run the script, headers doent have the PS_TOKEN and PS_LOGIN cookie parameter and only the PSJSESSIONID is present. We don't know how to solve this as we have also added Cookie Manager and tried with all the policy options available there (ex: compatibility, rfc.., default, etc) but nothing worked. Do we need to configure something else? Please help us to solve this. Thanks & Regards Sengamalam Kannan Testing CoE Mobile: +91 99529 67005 Tel: +91 44 6615 2684 -Original Message- From: Prakash, Ranjitha [mailto:ranjitha.prak...@aig.com] Sent: Thursday, April 30, 2009 6:14 PM To: JMeter Users List Subject: RE: Cookie Manager The recorded request header is the same as the browser request header. Thanks and Regards, Ranjitha Prakash Mob: 9884383831 Off: 66152735 It is easy to sit up and take notice. What is difficult is getting up and taking action -Original Message- From: Prakash, Ranjitha [mailto:ranjitha.prak...@aig.com] Sent: Thursday, April 30, 2009 5:51 PM To: JMeter Users List Subject: RE: Cookie Manager Given below is the request header Request Headers: Connection: keep-alive Host: 10.46.188.36:8080 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1) Accept-Language: en-us Referer: http://10.46.188.36:8080/psp/HR880TST/?cmd=login Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Thanks and Regards, Ranjitha Prakash Mob: 9884383831 Off: 66152735 It is easy to sit up and take notice. What is difficult is getting up and taking action -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Thursday, April 30, 2009 5:40 PM To: JMeter Users List Subject: Re: Cookie Manager What about the Requests? And how do these differ from the requests made by a browser? On 30/04/2009, Prakash, Ranjitha wrote: > These are the recorded script response headers in JMeter. But when we run the > script Response Headers doesn't have the PS_TOKEN, PS_LOGIN etc. Note that > we have also ncluded Cookie Manager. > > Response headers: > HTTP/1.1 200 OK > Date: Thu, 30 Apr 2009 11:25:04 GMT > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Encoding: gzip > Content-Length: 1853 > Content-Type: text/html; CHARSET=UTF-8 > Expires: Thu, 01 Dec 1994 16:00:00 GMT > UsesPortalRelativeURL: true > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:04_GMT; path=/ > PortalRegisteredURL: > http://10.46.188.36:8080/psc/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL > > Response headers: > HTTP/1.1 200 OK > Date: Thu, 30 Apr 2009 11:25:03 GMT > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Encoding: gzip > Content-Length: 716 > Content-Type: text/html; CHARSET=UTF-8 > Expires: Thu, 01 Dec 1994 16:00:00 GMT > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ > > > Response headers: > HTTP/1.1 302 Moved Temporarily > Date: Thu, 30 Apr 2009 11:25:00 GMT > Location: > http://10.46.188.36:8080/psp/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Type: text/html > Expires: Thu, 01 Dec 1994 16:00:00 GMT > Transfer-Encoding: Chunked > Set-Cookie: SignOnDefault=; expires=Thursday, 07-May-2009 11:25:03 GMT; > path=/ > Set-Cookie: > PS_TOKEN=sAQDAgEBvAIsBABTaGRyAk4AfQg4AC4AMQAwABSDa0+u3FOdXwNMa2yUaydpOJJjBnAFAFNkYXRhZHicHYpBDoJAEAQLJBx9gV9gs4H1sEcTXT0BAROPvsSf8TgrO53pztT0D+hObdOYR0udS2Fh46m/Wbmxq09ld/oHs6/zKiv+v7zkaSSqzKAnfTIHRhXcqx5lobaid7bFH4kfDgI=; > path=/ > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ > Set-Cookie: PS_LOGINLIST=http://10.46.188.36:8080/FP; path=/ > Set-Cookie: ExpirePage=http://10.46.188.36:8080/psp/FP/; path=/ > Connection: Close > > > Thanks and Regards, > Ranjitha Prakash > Mob: 9884383831 > Off: 66152735 > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > > -Original Message- > From: sebb [mailto:seb...@gmail.com] > Sent: Thursday, April 30, 2009 4:31 PM > To: JMeter Users List > Subject: Re: Cookie Manager > > http://wiki.apache.org/jakarta-jmeter/DifferentBehaviour > > On 30/04/2009, Prakash, Ranjitha wrote: > > Hi All, > > > > I am trying to do load test for a web page. I have enabled the > cookie
RE: Cookie Manager
The recorded request header is the same as the browser request header. Thanks and Regards, Ranjitha Prakash Mob: 9884383831 Off: 66152735 It is easy to sit up and take notice. What is difficult is getting up and taking action -Original Message- From: Prakash, Ranjitha [mailto:ranjitha.prak...@aig.com] Sent: Thursday, April 30, 2009 5:51 PM To: JMeter Users List Subject: RE: Cookie Manager Given below is the request header Request Headers: Connection: keep-alive Host: 10.46.188.36:8080 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1) Accept-Language: en-us Referer: http://10.46.188.36:8080/psp/HR880TST/?cmd=login Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Thanks and Regards, Ranjitha Prakash Mob: 9884383831 Off: 66152735 It is easy to sit up and take notice. What is difficult is getting up and taking action -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Thursday, April 30, 2009 5:40 PM To: JMeter Users List Subject: Re: Cookie Manager What about the Requests? And how do these differ from the requests made by a browser? On 30/04/2009, Prakash, Ranjitha wrote: > These are the recorded script response headers in JMeter. But when we run the > script Response Headers doesn't have the PS_TOKEN, PS_LOGIN etc. Note that > we have also ncluded Cookie Manager. > > Response headers: > HTTP/1.1 200 OK > Date: Thu, 30 Apr 2009 11:25:04 GMT > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Encoding: gzip > Content-Length: 1853 > Content-Type: text/html; CHARSET=UTF-8 > Expires: Thu, 01 Dec 1994 16:00:00 GMT > UsesPortalRelativeURL: true > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:04_GMT; path=/ > PortalRegisteredURL: > http://10.46.188.36:8080/psc/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL > > Response headers: > HTTP/1.1 200 OK > Date: Thu, 30 Apr 2009 11:25:03 GMT > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Encoding: gzip > Content-Length: 716 > Content-Type: text/html; CHARSET=UTF-8 > Expires: Thu, 01 Dec 1994 16:00:00 GMT > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ > > > Response headers: > HTTP/1.1 302 Moved Temporarily > Date: Thu, 30 Apr 2009 11:25:00 GMT > Location: > http://10.46.188.36:8080/psp/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Type: text/html > Expires: Thu, 01 Dec 1994 16:00:00 GMT > Transfer-Encoding: Chunked > Set-Cookie: SignOnDefault=; expires=Thursday, 07-May-2009 11:25:03 GMT; > path=/ > Set-Cookie: > PS_TOKEN=sAQDAgEBvAIsBABTaGRyAk4AfQg4AC4AMQAwABSDa0+u3FOdXwNMa2yUaydpOJJjBnAFAFNkYXRhZHicHYpBDoJAEAQLJBx9gV9gs4H1sEcTXT0BAROPvsSf8TgrO53pztT0D+hObdOYR0udS2Fh46m/Wbmxq09ld/oHs6/zKiv+v7zkaSSqzKAnfTIHRhXcqx5lobaid7bFH4kfDgI=; > path=/ > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ > Set-Cookie: PS_LOGINLIST=http://10.46.188.36:8080/FP; path=/ > Set-Cookie: ExpirePage=http://10.46.188.36:8080/psp/FP/; path=/ > Connection: Close > > > Thanks and Regards, > Ranjitha Prakash > Mob: 9884383831 > Off: 66152735 > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > > -Original Message- > From: sebb [mailto:seb...@gmail.com] > Sent: Thursday, April 30, 2009 4:31 PM > To: JMeter Users List > Subject: Re: Cookie Manager > > http://wiki.apache.org/jakarta-jmeter/DifferentBehaviour > > On 30/04/2009, Prakash, Ranjitha wrote: > > Hi All, > > > > I am trying to do load test for a web page. I have enabled the > cookie manager and all other required setup properly. But Still while doing > the load test, I am getting the following error message "You must have > cookies enabled in order to sign in to your application. Return to sign in > with cookies enabled." Please give me an appropriate solution for this error. > > > > > > > > Thanks and Regards, > > > > Ranjitha Prakash > > > > Mob: 9884383831 > > > > Off: 66152735 > > > > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > -
RE: Cookie Manager
Given below is the request header Request Headers: Connection: keep-alive Host: 10.46.188.36:8080 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1) Accept-Language: en-us Referer: http://10.46.188.36:8080/psp/HR880TST/?cmd=login Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Thanks and Regards, Ranjitha Prakash Mob: 9884383831 Off: 66152735 It is easy to sit up and take notice. What is difficult is getting up and taking action -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Thursday, April 30, 2009 5:40 PM To: JMeter Users List Subject: Re: Cookie Manager What about the Requests? And how do these differ from the requests made by a browser? On 30/04/2009, Prakash, Ranjitha wrote: > These are the recorded script response headers in JMeter. But when we run the > script Response Headers doesn't have the PS_TOKEN, PS_LOGIN etc. Note that > we have also ncluded Cookie Manager. > > Response headers: > HTTP/1.1 200 OK > Date: Thu, 30 Apr 2009 11:25:04 GMT > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Encoding: gzip > Content-Length: 1853 > Content-Type: text/html; CHARSET=UTF-8 > Expires: Thu, 01 Dec 1994 16:00:00 GMT > UsesPortalRelativeURL: true > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:04_GMT; path=/ > PortalRegisteredURL: > http://10.46.188.36:8080/psc/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL > > Response headers: > HTTP/1.1 200 OK > Date: Thu, 30 Apr 2009 11:25:03 GMT > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Encoding: gzip > Content-Length: 716 > Content-Type: text/html; CHARSET=UTF-8 > Expires: Thu, 01 Dec 1994 16:00:00 GMT > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ > > > Response headers: > HTTP/1.1 302 Moved Temporarily > Date: Thu, 30 Apr 2009 11:25:00 GMT > Location: > http://10.46.188.36:8080/psp/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Type: text/html > Expires: Thu, 01 Dec 1994 16:00:00 GMT > Transfer-Encoding: Chunked > Set-Cookie: SignOnDefault=; expires=Thursday, 07-May-2009 11:25:03 GMT; > path=/ > Set-Cookie: > PS_TOKEN=sAQDAgEBvAIsBABTaGRyAk4AfQg4AC4AMQAwABSDa0+u3FOdXwNMa2yUaydpOJJjBnAFAFNkYXRhZHicHYpBDoJAEAQLJBx9gV9gs4H1sEcTXT0BAROPvsSf8TgrO53pztT0D+hObdOYR0udS2Fh46m/Wbmxq09ld/oHs6/zKiv+v7zkaSSqzKAnfTIHRhXcqx5lobaid7bFH4kfDgI=; > path=/ > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ > Set-Cookie: PS_LOGINLIST=http://10.46.188.36:8080/FP; path=/ > Set-Cookie: ExpirePage=http://10.46.188.36:8080/psp/FP/; path=/ > Connection: Close > > > Thanks and Regards, > Ranjitha Prakash > Mob: 9884383831 > Off: 66152735 > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > > -Original Message- > From: sebb [mailto:seb...@gmail.com] > Sent: Thursday, April 30, 2009 4:31 PM > To: JMeter Users List > Subject: Re: Cookie Manager > > http://wiki.apache.org/jakarta-jmeter/DifferentBehaviour > > On 30/04/2009, Prakash, Ranjitha wrote: > > Hi All, > > > > I am trying to do load test for a web page. I have enabled the > cookie manager and all other required setup properly. But Still while doing > the load test, I am getting the following error message "You must have > cookies enabled in order to sign in to your application. Return to sign in > with cookies enabled." Please give me an appropriate solution for this error. > > > > > > > > Thanks and Regards, > > > > Ranjitha Prakash > > > > Mob: 9884383831 > > > > Off: 66152735 > > > > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: Cookie Manager
What about the Requests? And how do these differ from the requests made by a browser? On 30/04/2009, Prakash, Ranjitha wrote: > These are the recorded script response headers in JMeter. But when we run the > script Response Headers doesn't have the PS_TOKEN, PS_LOGIN etc. Note that > we have also ncluded Cookie Manager. > > Response headers: > HTTP/1.1 200 OK > Date: Thu, 30 Apr 2009 11:25:04 GMT > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Encoding: gzip > Content-Length: 1853 > Content-Type: text/html; CHARSET=UTF-8 > Expires: Thu, 01 Dec 1994 16:00:00 GMT > UsesPortalRelativeURL: true > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:04_GMT; path=/ > PortalRegisteredURL: > http://10.46.188.36:8080/psc/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL > > Response headers: > HTTP/1.1 200 OK > Date: Thu, 30 Apr 2009 11:25:03 GMT > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Encoding: gzip > Content-Length: 716 > Content-Type: text/html; CHARSET=UTF-8 > Expires: Thu, 01 Dec 1994 16:00:00 GMT > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ > > > Response headers: > HTTP/1.1 302 Moved Temporarily > Date: Thu, 30 Apr 2009 11:25:00 GMT > Location: > http://10.46.188.36:8080/psp/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL > Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 > 09:54:21 > Content-Type: text/html > Expires: Thu, 01 Dec 1994 16:00:00 GMT > Transfer-Encoding: Chunked > Set-Cookie: SignOnDefault=; expires=Thursday, 07-May-2009 11:25:03 GMT; > path=/ > Set-Cookie: > PS_TOKEN=sAQDAgEBvAIsBABTaGRyAk4AfQg4AC4AMQAwABSDa0+u3FOdXwNMa2yUaydpOJJjBnAFAFNkYXRhZHicHYpBDoJAEAQLJBx9gV9gs4H1sEcTXT0BAROPvsSf8TgrO53pztT0D+hObdOYR0udS2Fh46m/Wbmxq09ld/oHs6/zKiv+v7zkaSSqzKAnfTIHRhXcqx5lobaid7bFH4kfDgI=; > path=/ > Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ > Set-Cookie: PS_LOGINLIST=http://10.46.188.36:8080/FP; path=/ > Set-Cookie: ExpirePage=http://10.46.188.36:8080/psp/FP/; path=/ > Connection: Close > > > Thanks and Regards, > Ranjitha Prakash > Mob: 9884383831 > Off: 66152735 > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > > -Original Message- > From: sebb [mailto:seb...@gmail.com] > Sent: Thursday, April 30, 2009 4:31 PM > To: JMeter Users List > Subject: Re: Cookie Manager > > http://wiki.apache.org/jakarta-jmeter/DifferentBehaviour > > On 30/04/2009, Prakash, Ranjitha wrote: > > Hi All, > > > > I am trying to do load test for a web page. I have enabled the > cookie manager and all other required setup properly. But Still while doing > the load test, I am getting the following error message "You must have > cookies enabled in order to sign in to your application. Return to sign in > with cookies enabled." Please give me an appropriate solution for this error. > > > > > > > > Thanks and Regards, > > > > Ranjitha Prakash > > > > Mob: 9884383831 > > > > Off: 66152735 > > > > It is easy to sit up and take notice. What is difficult is getting up and > taking action > > > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
RE: Cookie Manager
These are the recorded script response headers in JMeter. But when we run the script Response Headers doesn't have the PS_TOKEN, PS_LOGIN etc. Note that we have also ncluded Cookie Manager. Response headers: HTTP/1.1 200 OK Date: Thu, 30 Apr 2009 11:25:04 GMT Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 09:54:21 Content-Encoding: gzip Content-Length: 1853 Content-Type: text/html; CHARSET=UTF-8 Expires: Thu, 01 Dec 1994 16:00:00 GMT UsesPortalRelativeURL: true Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:04_GMT; path=/ PortalRegisteredURL: http://10.46.188.36:8080/psc/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL Response headers: HTTP/1.1 200 OK Date: Thu, 30 Apr 2009 11:25:03 GMT Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 09:54:21 Content-Encoding: gzip Content-Length: 716 Content-Type: text/html; CHARSET=UTF-8 Expires: Thu, 01 Dec 1994 16:00:00 GMT Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ Response headers: HTTP/1.1 302 Moved Temporarily Date: Thu, 30 Apr 2009 11:25:00 GMT Location: http://10.46.188.36:8080/psp/FP/EMPLOYEE/HRMS/c/MAINTAIN_SECURITY.EMAIL_PSWD.GBL Server: WebLogic WebLogic Temporary patch 2 for PeopleSoft 04/30/2002 09:54:21 Content-Type: text/html Expires: Thu, 01 Dec 1994 16:00:00 GMT Transfer-Encoding: Chunked Set-Cookie: SignOnDefault=; expires=Thursday, 07-May-2009 11:25:03 GMT; path=/ Set-Cookie: PS_TOKEN=sAQDAgEBvAIsBABTaGRyAk4AfQg4AC4AMQAwABSDa0+u3FOdXwNMa2yUaydpOJJjBnAFAFNkYXRhZHicHYpBDoJAEAQLJBx9gV9gs4H1sEcTXT0BAROPvsSf8TgrO53pztT0D+hObdOYR0udS2Fh46m/Wbmxq09ld/oHs6/zKiv+v7zkaSSqzKAnfTIHRhXcqx5lobaid7bFH4kfDgI=; path=/ Set-Cookie: PS_TOKENEXPIRE=30_Apr_2009_11:25:03_GMT; path=/ Set-Cookie: PS_LOGINLIST=http://10.46.188.36:8080/FP; path=/ Set-Cookie: ExpirePage=http://10.46.188.36:8080/psp/FP/; path=/ Connection: Close Thanks and Regards, Ranjitha Prakash Mob: 9884383831 Off: 66152735 It is easy to sit up and take notice. What is difficult is getting up and taking action -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Thursday, April 30, 2009 4:31 PM To: JMeter Users List Subject: Re: Cookie Manager http://wiki.apache.org/jakarta-jmeter/DifferentBehaviour On 30/04/2009, Prakash, Ranjitha wrote: > Hi All, > > I am trying to do load test for a web page. I have enabled the > cookie manager and all other required setup properly. But Still while doing > the load test, I am getting the following error message "You must have > cookies enabled in order to sign in to your application. Return to sign in > with cookies enabled." Please give me an appropriate solution for this error. > > > > Thanks and Regards, > > Ranjitha Prakash > > Mob: 9884383831 > > Off: 66152735 > > It is easy to sit up and take notice. What is difficult is getting up and > taking action > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: Cookie Manager
http://wiki.apache.org/jakarta-jmeter/DifferentBehaviour On 30/04/2009, Prakash, Ranjitha wrote: > Hi All, > > I am trying to do load test for a web page. I have enabled the > cookie manager and all other required setup properly. But Still while doing > the load test, I am getting the following error message "You must have > cookies enabled in order to sign in to your application. Return to sign in > with cookies enabled." Please give me an appropriate solution for this error. > > > > Thanks and Regards, > > Ranjitha Prakash > > Mob: 9884383831 > > Off: 66152735 > > It is easy to sit up and take notice. What is difficult is getting up and > taking action > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Cookie Manager
Hi All, I am trying to do load test for a web page. I have enabled the cookie manager and all other required setup properly. But Still while doing the load test, I am getting the following error message "You must have cookies enabled in order to sign in to your application. Return to sign in with cookies enabled." Please give me an appropriate solution for this error. Thanks and Regards, Ranjitha Prakash Mob: 9884383831 Off: 66152735 It is easy to sit up and take notice. What is difficult is getting up and taking action
Re: Cookie Manager with Include Controller
On 20/04/2009, drubix wrote: > > Hi, > > I have a test plan that includes 4 elements: > * HTTP Cookie Manager > * Login request > * Request to secure page > * Logout request > > This works perfectly. Now, I want to encapsulate the login and logout > requests into separate jmx files so that they can be included in multiple > different test plans using Include Controllers. However, I can't figure out > where to put the HTTP Cookie Manager so that the jsession ID generated by > the login request is used in the top level plan for the request to the > secure page. I've tried to place it in both "login.jmx" and the top level > test plan that includes "login.jmx" using an Include Controller but in both > situations the Jsession ID returned from the login request isn't used for > the secure page request. It should just work if the Cookie Manager is left in the main test plan. > Is this a supported feature or should I just manually add the login request > and logout request to each test plan? > > Thanks, > > Drew > > -- > View this message in context: > http://www.nabble.com/Cookie-Manager-with-Include-Controller-tp23129747p23129747.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Cookie Manager with Include Controller
Hi, I have a test plan that includes 4 elements: * HTTP Cookie Manager * Login request * Request to secure page * Logout request This works perfectly. Now, I want to encapsulate the login and logout requests into separate jmx files so that they can be included in multiple different test plans using Include Controllers. However, I can't figure out where to put the HTTP Cookie Manager so that the jsession ID generated by the login request is used in the top level plan for the request to the secure page. I've tried to place it in both "login.jmx" and the top level test plan that includes "login.jmx" using an Include Controller but in both situations the Jsession ID returned from the login request isn't used for the secure page request. Is this a supported feature or should I just manually add the login request and logout request to each test plan? Thanks, Drew -- View this message in context: http://www.nabble.com/Cookie-Manager-with-Include-Controller-tp23129747p23129747.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: HTTP cookie manager and cross domain cookies
On 13/03/2009, Asanov, Leo wrote:
> Thanks!
> Is there any workaround I can use for the moment? Given that I can't
> change amtst.sensis.com.au:50080/amserver/UI/Login (step 2) behaviour.
>
If you are willing to try a nightly build, I put a fix into SVN which
is in builds after r753086. This should stop cross-domain cookies from
being stored.
It is also possible to maniulate the cookie jar using a BeanShell
Post-Processor.
// Get the jar of cookies
cm=ctx.getCurrentSampler().getCookieManager();
jar=cm.getCookies();
// Loop through the cookies
iter = jar.iterator();
while (iter.hasNext()) {
cookie = iter.next().getObjectValue();
if (".integrators.com".equals(cookie.getDomain())){
iter.remove();
}
}
This does not take account of cookies for ".integrators.com" that may
previously have been legitimately added to the jar. You might need to
narrow the match using the cookie name as well.
See the Javadocs for methods you can call on the objects:
http://jakarta.apache.org/jmeter/api/index.html
e.g.
http://jakarta.apache.org/jmeter/api/org/apache/jmeter/protocol/http/control/Cookie.html
> Cheers,
> Leo
>
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
>
> Sent: Friday, 13 March 2009 12:29 PM
> To: JMeter Users List
> Subject: Re: HTTP cookie manager and cross domain cookies
>
> On 12/03/2009, Asanov, Leo wrote:
> > >What cookies are sent at step 1?
> > >What cookies are returned from step 1?
> > >What cookies are sent in step 2?
> >
> >
> > This is the behaviour I observe in JMeter
> > ___
> >
> > Step 1: GET http://samplesite.integrators.com/Samplesite/login.html
> > Cookies: JSESSIONID=blah
> >
> > Step 2: POST to http://amtst.sensis.com.au:50080/amserver/UI/Login
> > (no cookies are sent)
> >
> > HTTP/1.1 302 Moved Temporarily
> > Location: http://samplesite.integrators.com:80/Samplesite/home.html
> >
> > Set-cookie: amlbcookie=01; Domain=.sensis.com.au; Path=/
> > Set-cookie: amlbcookie=01; Domain=.integrators.com; Path=/
> > Set-cookie: iPlanetDirectoryPro=blah; Domain=.sensis.com.au; Path=/
> > Set-cookie: iPlanetDirectoryPro=blah; Domain=.integrators.com; Path=/
> >
> > Step 3: GET http://samplesite.integrators.com/Samplesite/home.html
> > Cookies:
> > JSESSIONID=blah; amlbcookie=01; iPlanetDirectoryPro=blah;
> >
> > HTTP/1.1 200 OK
> > home.html content
> >
> > (The "iPlanetDirectoryPro" value is identical to the step 2.)
> > ___
> >
> > This is what's happening in the browser.
> > ___
> >
> > Step 1: GET http://samplesite.integrators.com/Samplesite/login.html
> > Cookies: JSESSIONID=blah
> >
> > Step 2: POST http://amtst.sensis.com.au:50080/amserver/UI/Login
> > (no cookies are sent)
> >
> > HTTP/1.1 302 Moved Temporarily
> > Location: http://samplesite.integrators.com:80/Samplesite/home.html
> >
> > Set-cookie: amlbcookie=01; Domain=.sensis.com.au; Path=/
> > Set-cookie: amlbcookie=01; Domain=.integrators.com; Path=/
> > Set-cookie: iPlanetDirectoryPro=blah; Domain=.sensis.com.au; Path=/
> > Set-cookie: iPlanetDirectoryPro=blah; Domain=.integrators.com; Path=/
> >
> > Step 3: GET http://samplesite.integrators.com/Samplesite/home.html
> > Cookies: JSESSIONID=blah
> >
> > HTTP/1.1 302 Found
> > And the redirect to cross domain verification mechanism.
> >
> > ___
> >
> > So what's happening is that domain amtst.sensis.com.au is setting the
> > "iPlanetDirectoryPro" cookie for domain .integrators.com and that
> > doesn't work in the browser and works in JMeter. I wonder if that's
> > because the server sends 302 with further redirection to
> > .integrators.com at the step 2.
>
> Thanks, that's a very clear description of what's happening.
>
> It looks like the code just extracts all the cookies and stores them,
> regardless of whether they are for the correct domain or not.
>
> This will be fixed for the next release - thanks for reporting the
> problem.
>
> > Cheers,
> > Leo
> >
> >
> > -Original Message-
> > From: sebb [mailto:seb...@gmail.com]
> > Sent: Wednesday, 11 March 2009 11:53 PM
> > To: JMeter Users List
> > Subject: Re: HTTP cookie manager and cross domain cookies
> >
> > On 11/03/2009, Asanov, Leo wrote:
> > >
> > > Hi,
> > >
> > > It appears that HTTP cookie manager allows
RE: HTTP cookie manager and cross domain cookies
Thanks! Is there any workaround I can use for the moment? Given that I can't change amtst.sensis.com.au:50080/amserver/UI/Login (step 2) behaviour. Cheers, Leo -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Friday, 13 March 2009 12:29 PM To: JMeter Users List Subject: Re: HTTP cookie manager and cross domain cookies On 12/03/2009, Asanov, Leo wrote: > >What cookies are sent at step 1? > >What cookies are returned from step 1? > >What cookies are sent in step 2? > > > This is the behaviour I observe in JMeter > ___ > > Step 1: GET http://samplesite.integrators.com/Samplesite/login.html > Cookies: JSESSIONID=blah > > Step 2: POST to http://amtst.sensis.com.au:50080/amserver/UI/Login > (no cookies are sent) > > HTTP/1.1 302 Moved Temporarily > Location: http://samplesite.integrators.com:80/Samplesite/home.html > > Set-cookie: amlbcookie=01; Domain=.sensis.com.au; Path=/ > Set-cookie: amlbcookie=01; Domain=.integrators.com; Path=/ > Set-cookie: iPlanetDirectoryPro=blah; Domain=.sensis.com.au; Path=/ > Set-cookie: iPlanetDirectoryPro=blah; Domain=.integrators.com; Path=/ > > Step 3: GET http://samplesite.integrators.com/Samplesite/home.html > Cookies: > JSESSIONID=blah; amlbcookie=01; iPlanetDirectoryPro=blah; > > HTTP/1.1 200 OK > home.html content > > (The "iPlanetDirectoryPro" value is identical to the step 2.) > ___ > > This is what's happening in the browser. > ___ > > Step 1: GET http://samplesite.integrators.com/Samplesite/login.html > Cookies: JSESSIONID=blah > > Step 2: POST http://amtst.sensis.com.au:50080/amserver/UI/Login > (no cookies are sent) > > HTTP/1.1 302 Moved Temporarily > Location: http://samplesite.integrators.com:80/Samplesite/home.html > > Set-cookie: amlbcookie=01; Domain=.sensis.com.au; Path=/ > Set-cookie: amlbcookie=01; Domain=.integrators.com; Path=/ > Set-cookie: iPlanetDirectoryPro=blah; Domain=.sensis.com.au; Path=/ > Set-cookie: iPlanetDirectoryPro=blah; Domain=.integrators.com; Path=/ > > Step 3: GET http://samplesite.integrators.com/Samplesite/home.html > Cookies: JSESSIONID=blah > > HTTP/1.1 302 Found > And the redirect to cross domain verification mechanism. > > ___ > > So what's happening is that domain amtst.sensis.com.au is setting the > "iPlanetDirectoryPro" cookie for domain .integrators.com and that > doesn't work in the browser and works in JMeter. I wonder if that's > because the server sends 302 with further redirection to > .integrators.com at the step 2. Thanks, that's a very clear description of what's happening. It looks like the code just extracts all the cookies and stores them, regardless of whether they are for the correct domain or not. This will be fixed for the next release - thanks for reporting the problem. > Cheers, > Leo > > > -Original Message----- > From: sebb [mailto:seb...@gmail.com] > Sent: Wednesday, 11 March 2009 11:53 PM > To: JMeter Users List > Subject: Re: HTTP cookie manager and cross domain cookies > > On 11/03/2009, Asanov, Leo wrote: > > > > Hi, > > > > It appears that HTTP cookie manager allows cross domain cookies, > which > > is different to the behaviour of the browsers. I'm writing a test for > an > > application, which is using Identity Management platform with cross > > domain single sign on. The chain of event is the following: > > > > > > > > 111.com - website domain > > > > 222.com - identity management domain (different to the first domain) > > > > > > > > 1. Login page on 111.com - sends request to 222.com with the > > entered user credentials. 222.com sets cookies with authentication > > information for both 222.com, and 111.com and redirects back to > 111.com > > So there is a cookie for 111.com? > > > 2. Since it's a different domain, the cookie for 111.com isn't > set, > > so it has to do a couple of redirects to check if the user is > authorised > > to see the page and only then returns the page. > > > > > > > > That's how it works in the browser. In JMeter I can clearly see that > at > > the step 2 cookies for domain 111.com are passed through and the > > requested page is returned straight away. I tried different "Cookie > > policy" settings, didn't help. > > > > > > > > I don't think that's how it supposed to work, can anyone comment on > > that? I'm using JMeter 2.3.2, "HTTP Request" sampler with
Re: HTTP cookie manager and cross domain cookies
On 12/03/2009, Asanov, Leo wrote: > >What cookies are sent at step 1? > >What cookies are returned from step 1? > >What cookies are sent in step 2? > > > This is the behaviour I observe in JMeter > ___ > > Step 1: GET http://samplesite.integrators.com/Samplesite/login.html > Cookies: JSESSIONID=blah > > Step 2: POST to http://amtst.sensis.com.au:50080/amserver/UI/Login > (no cookies are sent) > > HTTP/1.1 302 Moved Temporarily > Location: http://samplesite.integrators.com:80/Samplesite/home.html > > Set-cookie: amlbcookie=01; Domain=.sensis.com.au; Path=/ > Set-cookie: amlbcookie=01; Domain=.integrators.com; Path=/ > Set-cookie: iPlanetDirectoryPro=blah; Domain=.sensis.com.au; Path=/ > Set-cookie: iPlanetDirectoryPro=blah; Domain=.integrators.com; Path=/ > > Step 3: GET http://samplesite.integrators.com/Samplesite/home.html > Cookies: > JSESSIONID=blah; amlbcookie=01; iPlanetDirectoryPro=blah; > > HTTP/1.1 200 OK > home.html content > > (The "iPlanetDirectoryPro" value is identical to the step 2.) > ___ > > This is what's happening in the browser. > ___ > > Step 1: GET http://samplesite.integrators.com/Samplesite/login.html > Cookies: JSESSIONID=blah > > Step 2: POST http://amtst.sensis.com.au:50080/amserver/UI/Login > (no cookies are sent) > > HTTP/1.1 302 Moved Temporarily > Location: http://samplesite.integrators.com:80/Samplesite/home.html > > Set-cookie: amlbcookie=01; Domain=.sensis.com.au; Path=/ > Set-cookie: amlbcookie=01; Domain=.integrators.com; Path=/ > Set-cookie: iPlanetDirectoryPro=blah; Domain=.sensis.com.au; Path=/ > Set-cookie: iPlanetDirectoryPro=blah; Domain=.integrators.com; Path=/ > > Step 3: GET http://samplesite.integrators.com/Samplesite/home.html > Cookies: JSESSIONID=blah > > HTTP/1.1 302 Found > And the redirect to cross domain verification mechanism. > > ___ > > So what's happening is that domain amtst.sensis.com.au is setting the > "iPlanetDirectoryPro" cookie for domain .integrators.com and that > doesn't work in the browser and works in JMeter. I wonder if that's > because the server sends 302 with further redirection to > .integrators.com at the step 2. Thanks, that's a very clear description of what's happening. It looks like the code just extracts all the cookies and stores them, regardless of whether they are for the correct domain or not. This will be fixed for the next release - thanks for reporting the problem. > Cheers, > Leo > > > -Original Message----- > From: sebb [mailto:seb...@gmail.com] > Sent: Wednesday, 11 March 2009 11:53 PM > To: JMeter Users List > Subject: Re: HTTP cookie manager and cross domain cookies > > On 11/03/2009, Asanov, Leo wrote: > > > > Hi, > > > > It appears that HTTP cookie manager allows cross domain cookies, > which > > is different to the behaviour of the browsers. I'm writing a test for > an > > application, which is using Identity Management platform with cross > > domain single sign on. The chain of event is the following: > > > > > > > > 111.com - website domain > > > > 222.com - identity management domain (different to the first domain) > > > > > > > > 1. Login page on 111.com - sends request to 222.com with the > > entered user credentials. 222.com sets cookies with authentication > > information for both 222.com, and 111.com and redirects back to > 111.com > > So there is a cookie for 111.com? > > > 2. Since it's a different domain, the cookie for 111.com isn't > set, > > so it has to do a couple of redirects to check if the user is > authorised > > to see the page and only then returns the page. > > > > > > > > That's how it works in the browser. In JMeter I can clearly see that > at > > the step 2 cookies for domain 111.com are passed through and the > > requested page is returned straight away. I tried different "Cookie > > policy" settings, didn't help. > > > > > > > > I don't think that's how it supposed to work, can anyone comment on > > that? I'm using JMeter 2.3.2, "HTTP Request" sampler with "Follow > > redirects" and "Redirect automatically" turned off. > > > > What cookies are sent at step 1? > What cookies are returned from step 1? > What cookies are sent in step 2? > > You may change the names and values for privacy, but please don't > leave out any parts of th
RE: HTTP cookie manager and cross domain cookies
>What cookies are sent at step 1? >What cookies are returned from step 1? >What cookies are sent in step 2? This is the behaviour I observe in JMeter ___ Step 1: GET http://samplesite.integrators.com/Samplesite/login.html Cookies: JSESSIONID=blah Step 2: POST to http://amtst.sensis.com.au:50080/amserver/UI/Login (no cookies are sent) HTTP/1.1 302 Moved Temporarily Location: http://samplesite.integrators.com:80/Samplesite/home.html Set-cookie: amlbcookie=01; Domain=.sensis.com.au; Path=/ Set-cookie: amlbcookie=01; Domain=.integrators.com; Path=/ Set-cookie: iPlanetDirectoryPro=blah; Domain=.sensis.com.au; Path=/ Set-cookie: iPlanetDirectoryPro=blah; Domain=.integrators.com; Path=/ Step 3: GET http://samplesite.integrators.com/Samplesite/home.html Cookies: JSESSIONID=blah; amlbcookie=01; iPlanetDirectoryPro=blah; HTTP/1.1 200 OK home.html content (The "iPlanetDirectoryPro" value is identical to the step 2.) ___ This is what's happening in the browser. ___ Step 1: GET http://samplesite.integrators.com/Samplesite/login.html Cookies: JSESSIONID=blah Step 2: POST http://amtst.sensis.com.au:50080/amserver/UI/Login (no cookies are sent) HTTP/1.1 302 Moved Temporarily Location: http://samplesite.integrators.com:80/Samplesite/home.html Set-cookie: amlbcookie=01; Domain=.sensis.com.au; Path=/ Set-cookie: amlbcookie=01; Domain=.integrators.com; Path=/ Set-cookie: iPlanetDirectoryPro=blah; Domain=.sensis.com.au; Path=/ Set-cookie: iPlanetDirectoryPro=blah; Domain=.integrators.com; Path=/ Step 3: GET http://samplesite.integrators.com/Samplesite/home.html Cookies: JSESSIONID=blah HTTP/1.1 302 Found And the redirect to cross domain verification mechanism. ___ So what's happening is that domain amtst.sensis.com.au is setting the "iPlanetDirectoryPro" cookie for domain .integrators.com and that doesn't work in the browser and works in JMeter. I wonder if that's because the server sends 302 with further redirection to .integrators.com at the step 2. Cheers, Leo -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Wednesday, 11 March 2009 11:53 PM To: JMeter Users List Subject: Re: HTTP cookie manager and cross domain cookies On 11/03/2009, Asanov, Leo wrote: > > Hi, > > It appears that HTTP cookie manager allows cross domain cookies, which > is different to the behaviour of the browsers. I'm writing a test for an > application, which is using Identity Management platform with cross > domain single sign on. The chain of event is the following: > > > > 111.com - website domain > > 222.com - identity management domain (different to the first domain) > > > > 1. Login page on 111.com - sends request to 222.com with the > entered user credentials. 222.com sets cookies with authentication > information for both 222.com, and 111.com and redirects back to 111.com So there is a cookie for 111.com? > 2. Since it's a different domain, the cookie for 111.com isn't set, > so it has to do a couple of redirects to check if the user is authorised > to see the page and only then returns the page. > > > > That's how it works in the browser. In JMeter I can clearly see that at > the step 2 cookies for domain 111.com are passed through and the > requested page is returned straight away. I tried different "Cookie > policy" settings, didn't help. > > > > I don't think that's how it supposed to work, can anyone comment on > that? I'm using JMeter 2.3.2, "HTTP Request" sampler with "Follow > redirects" and "Redirect automatically" turned off. > What cookies are sent at step 1? What cookies are returned from step 1? What cookies are sent in step 2? You may change the names and values for privacy, but please don't leave out any parts of the host name. > > Cheers, > > Leo > > > > Sensis. Helping you find, buy and sell. > > www.sensis.com.au - www.yellow.com.au - www.whitepages.com.au - www.citysearch.com.au - www.whereis.com.au - www.tradingpost.com.au > > Sensis cares for the environment - think before you print. > > This email and any attachments are intended only for the use of the recipient and may be confidential and/or legally privileged. Sensis Pty Ltd disclaims liability for any errors, omissions, viruses, loss and/or damage arising from using, opening or transmitting this email. If you are not the intended recipient you must not use, interfere with, disclose, copy or retain this email and you should notify the sender immediately by return email or by contacting Sensis Pty Ltd by telephone on [+61 3 8653 5000] - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: HTTP cookie manager and cross domain cookies
On 11/03/2009, Asanov, Leo wrote: > > Hi, > > It appears that HTTP cookie manager allows cross domain cookies, which > is different to the behaviour of the browsers. I'm writing a test for an > application, which is using Identity Management platform with cross > domain single sign on. The chain of event is the following: > > > > 111.com - website domain > > 222.com - identity management domain (different to the first domain) > > > > 1. Login page on 111.com - sends request to 222.com with the > entered user credentials. 222.com sets cookies with authentication > information for both 222.com, and 111.com and redirects back to 111.com So there is a cookie for 111.com? > 2. Since it's a different domain, the cookie for 111.com isn't set, > so it has to do a couple of redirects to check if the user is authorised > to see the page and only then returns the page. > > > > That's how it works in the browser. In JMeter I can clearly see that at > the step 2 cookies for domain 111.com are passed through and the > requested page is returned straight away. I tried different "Cookie > policy" settings, didn't help. > > > > I don't think that's how it supposed to work, can anyone comment on > that? I'm using JMeter 2.3.2, "HTTP Request" sampler with "Follow > redirects" and "Redirect automatically" turned off. > What cookies are sent at step 1? What cookies are returned from step 1? What cookies are sent in step 2? You may change the names and values for privacy, but please don't leave out any parts of the host name. > > Cheers, > > Leo > > > > Sensis. Helping you find, buy and sell. > > www.sensis.com.au - www.yellow.com.au - www.whitepages.com.au - > www.citysearch.com.au - www.whereis.com.au - www.tradingpost.com.au > > Sensis cares for the environment - think before you print. > > This email and any attachments are intended only for the use of the > recipient and may be confidential and/or legally privileged. Sensis Pty Ltd > disclaims liability for any errors, omissions, viruses, loss and/or damage > arising from using, opening or transmitting this email. If you are not the > intended recipient you must not use, interfere with, disclose, copy or retain > this email and you should notify the sender immediately by return email or by > contacting Sensis Pty Ltd by telephone on [+61 3 8653 5000] - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
HTTP cookie manager and cross domain cookies
Hi, It appears that HTTP cookie manager allows cross domain cookies, which is different to the behaviour of the browsers. I'm writing a test for an application, which is using Identity Management platform with cross domain single sign on. The chain of event is the following: 111.com - website domain 222.com - identity management domain (different to the first domain) 1. Login page on 111.com - sends request to 222.com with the entered user credentials. 222.com sets cookies with authentication information for both 222.com, and 111.com and redirects back to 111.com 2. Since it's a different domain, the cookie for 111.com isn't set, so it has to do a couple of redirects to check if the user is authorised to see the page and only then returns the page. That's how it works in the browser. In JMeter I can clearly see that at the step 2 cookies for domain 111.com are passed through and the requested page is returned straight away. I tried different "Cookie policy" settings, didn't help. I don't think that's how it supposed to work, can anyone comment on that? I'm using JMeter 2.3.2, "HTTP Request" sampler with "Follow redirects" and "Redirect automatically" turned off. Cheers, Leo Sensis. Helping you find, buy and sell. www.sensis.com.au - www.yellow.com.au - www.whitepages.com.au - www.citysearch.com.au - www.whereis.com.au - www.tradingpost.com.au Sensis cares for the environment - think before you print. This email and any attachments are intended only for the use of the recipient and may be confidential and/or legally privileged. Sensis Pty Ltd disclaims liability for any errors, omissions, viruses, loss and/or damage arising from using, opening or transmitting this email. If you are not the intended recipient you must not use, interfere with, disclose, copy or retain this email and you should notify the sender immediately by return email or by contacting Sensis Pty Ltd by telephone on [+61 3 8653 5000]
Re: Http Cookie Manager and jsessionid
On 09/01/2009, Maya Hague wrote: > I have a very similar problem as this and I'm in desperate need for help. > Thanks in advance. maya > > My test plan includes a threadgroup with the following. Thread Group > >> ++HTTP Cookie Manager > >> ++WebService(SOAP) Request > >> ++WebService(SOAP) Request > >> ++WebService(SOAP) Request > >> ++WebService(SOAP) Request > >> ++View Results Tree > > And I need the sessionid in the first soap call to persist for the rest of > the soap calls. I tried using soap/xml rpc request, but I have to call that > soap/xml rpc request before the every request that I am interested in. How is the sessionid passed? Is it a cookie? > This is what I did, but I would like to make only 1 call to the >> soap/xml > rpc_new1 > > >> ++HTTP Cookie Manager > >> soap/xml rpc_new1 > >> ++WebService(SOAP) Request (I cannot change this to an soap/xml rpc > because the response is incorrect) I don't understand why not, it should be able to send any request. Maybe you need to add a Header Manager. > >> soap/xml rpc_new1 > >> ++WebService(SOAP) Request > >> soap/xml rpc_new1 > >> ++WebService(SOAP) Request > >> ++View Results Tree > I don't understand how the session id is working - if it passes from the RPC sampler to the WebService sampler, why is it not passing to the next WebService sampler. There must be something else going on here which has not been described. > - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: Http Cookie Manager and jsessionid
I have a very similar problem as this and I'm in desperate need for help. Thanks in advance. maya My test plan includes a threadgroup with the following. Thread Group >> ++HTTP Cookie Manager >> ++WebService(SOAP) Request >> ++WebService(SOAP) Request >> ++WebService(SOAP) Request >> ++WebService(SOAP) Request >> ++View Results Tree And I need the sessionid in the first soap call to persist for the rest of the soap calls. I tried using soap/xml rpc request, but I have to call that soap/xml rpc request before the every request that I am interested in. This is what I did, but I would like to make only 1 call to the >> soap/xml rpc_new1 >> ++HTTP Cookie Manager >> soap/xml rpc_new1 >> ++WebService(SOAP) Request (I cannot change this to an soap/xml rpc because >> the response is incorrect) >> soap/xml rpc_new1 >> ++WebService(SOAP) Request >> soap/xml rpc_new1 >> ++WebService(SOAP) Request >> ++View Results Tree
Re: Cookie Manager -- JSESSIONID reused
2008/5/6 Jason Frank <[EMAIL PROTECTED]>: > I am using JMeter 2.3.1 to test a java (Tomcat) web application. My test > involves a login, followed by an action that requires the user to be logged > in. I use an HTTP Cookie Manager in the Thread Group so that the second > request will be recognized as "logged in", due to the JSESSIONID cookie that > gets assigned during login. > > I want to be able to "loop" over my test, so that it is repeated multiple > times. Therefore, I check the "clear cookies each iteration" box, so that on > the second iteration it will not reuse the JSESSIONID that was assigned the > first time. So far, so good. I can see the POST to my login page has no > cookies each time, and the response contains a SET-COOKIE directive for > JSESSIONID. > > The problem comes when I want to use multiple threads. Suppose I launch 2 > threads for this Thread Group. Thread A makes a POST to the login page, with > no cookies, and gets a response to set the JSESSIONID cookie. Then, Thread B > makes a POST to the login page, and (here is what I think the root of the > problem is) it sends the same cookie value of JSESSIONID that Thread A > received. The response to Thread B tells it to set a different value for > JSESSIONID, so usually this results in two separate logins, but this doesn't > always happen. The result is that I sometimes have both threads using the > same value for JSESSIONID, which causes problems later in my test. > > Interestingly, if I don't check the box for "clear cookies each iteration", > then Thread A and Thread B work fine -- Thread B's POST to the login page has > no cookies, as it should. However, this gets me into trouble when the > threads go back for another iteration. So I can set things up to *either* > work for multiple threads, or for multiple loops, but not both. > > Has anyone seen this behavior? Is this a JMeter bug, or something that I am > misunderstanding? > http://wiki.apache.org/jakarta-jmeter/CookieManagerBugIn231 > > > > > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > - > 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]
Cookie Manager -- JSESSIONID reused
I am using JMeter 2.3.1 to test a java (Tomcat) web application. My test involves a login, followed by an action that requires the user to be logged in. I use an HTTP Cookie Manager in the Thread Group so that the second request will be recognized as "logged in", due to the JSESSIONID cookie that gets assigned during login. I want to be able to "loop" over my test, so that it is repeated multiple times. Therefore, I check the "clear cookies each iteration" box, so that on the second iteration it will not reuse the JSESSIONID that was assigned the first time. So far, so good. I can see the POST to my login page has no cookies each time, and the response contains a SET-COOKIE directive for JSESSIONID. The problem comes when I want to use multiple threads. Suppose I launch 2 threads for this Thread Group. Thread A makes a POST to the login page, with no cookies, and gets a response to set the JSESSIONID cookie. Then, Thread B makes a POST to the login page, and (here is what I think the root of the problem is) it sends the same cookie value of JSESSIONID that Thread A received. The response to Thread B tells it to set a different value for JSESSIONID, so usually this results in two separate logins, but this doesn't always happen. The result is that I sometimes have both threads using the same value for JSESSIONID, which causes problems later in my test. Interestingly, if I don't check the box for "clear cookies each iteration", then Thread A and Thread B work fine -- Thread B's POST to the login page has no cookies, as it should. However, this gets me into trouble when the threads go back for another iteration. So I can set things up to *either* work for multiple threads, or for multiple loops, but not both. Has anyone seen this behavior? Is this a JMeter bug, or something that I am misunderstanding? Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Odd Cookie Manager behavior
Known bug, see: http://wiki.apache.org/jakarta-jmeter/CookieManagerBugIn231 On 14/04/2008, Peter Guarnieri <[EMAIL PROTECTED]> wrote: > Hey All, > I was wondering if anyone could offer some advice on how to deal with an odd > issue I'm seeing with my Jmeter test. It's a simple test that logs into a > webapp, and it looks roughly like this: > > Thread group > | > -HTTPCookieManager > -Simple Controller > | --Login (HTTP Request that posts the user name and password to a Netegrity > Siteminder action) > | --Get Homepage (HTTP Request that gets the homepage of the app) > -View Results Tree > -Aggregate Report > > I have the "Clear cookies each iteration?" option set to true in my > HTTPCookieManager. The thread group has 5 users, with a 1 second ramp up > period, and only one iteration. The problem is that when I look at the View > Results Tree report, I can see that only the first thread sends the 'Login' > action with no cookies. The subsequent 4 threads all send a cookie who's > value was set by the previous thread. As suggested on this list, I switched > on debugging for the HTTPCookieManager, and got this stack trace: > > > 2008/04/14 17:09:25 INFO - jmeter.engine.StandardJMeterEngine: Running the > test! > 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: > Clear all cookies from store > 2008/04/14 17:09:25 INFO - jmeter.gui.util.JMeterMenuBar: > setRunning(true,*local*) > 2008/04/14 17:09:25 INFO - jmeter.engine.StandardJMeterEngine: Starting 5 > threads for group Test Execution. Ramp up = 5. > 2008/04/14 17:09:25 INFO - jmeter.engine.StandardJMeterEngine: Continue on > error > 2008/04/14 17:09:25 INFO - jmeter.threads.JMeterThread: Thread Test > Execution 1-1 started > 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: > Clear all cookies from store > 2008/04/14 17:09:25 INFO - jmeter.services.FileServer: Stored: > C:\jakarta-jmeter-2.3.1\test plans\users.csv > 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: > Found 0 cookies for https://my.site.com/suite/login/login.fcc > 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: > Received Cookie: > FORMCRED=ilBWOQVZ8OyBxrpjczIyJuO5Zj9reyJCi3E77fw1VmbC5pSM3ls5KmQbpsjCpwOhDC1MtHLBe3uBJTHMx2qo05Wh2yf3YkD3AiQjVhFUSRVl3eD0vIEu84cQH9uRXVje;path=/; > domain=.site.com From: https://my.site.com/suite/login/login.fcc > 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: Add > cookie to store .site.com TRUE / FALSE 0 FORMCRED > ilBWOQVZ8OyBxrpjczIyJuO5Zj9reyJCi3E77fw1VmbC5pSM3ls5KmQbpsjCpwOhDC1MtHLBe3uBJTHMx2qo05Wh2yf3YkD3AiQjVhFUSRVl3eD0vIEu84cQH9uRXVje > 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: > Found 1 cookies for https://my.site.com/suite/portal/authenticate.do > 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: > Cookie: > FORMCRED=ilBWOQVZ8OyBxrpjczIyJuO5Zj9reyJCi3E77fw1VmbC5pSM3ls5KmQbpsjCpwOhDC1MtHLBe3uBJTHMx2qo05Wh2yf3YkD3AiQjVhFUSRVl3eD0vIEu84cQH9uRXVje > 2008/04/14 17:09:26 DEBUG - jmeter.protocol.http.control.CookieManager: > Received Cookie: FORMCRED=; path=/; expires=Wed, 17 Oct 2007 21:09:25 GMT; > domain=.site.com From: https://my.site.com/suite/portal/authenticate.do > 2008/04/14 17:09:26 DEBUG - jmeter.protocol.http.control.CookieManager: New > Cookie = .site.com TRUE / FALSE 1192655365 FORMCRED removing matching Cookie > .site.com TRUE / FALSE 0 FORMCRED > ilBWOQVZ8OyBxrpjczIyJuO5Zj9reyJCi3E77fw1VmbC5pSM3ls5KmQbpsjCpwOhDC1MtHLBe3uBJTHMx2qo05Wh2yf3YkD3AiQjVhFUSRVl3eD0vIEu84cQH9uRXVje > 2008/04/14 17:09:26 DEBUG - jmeter.protocol.http.control.CookieManager: > Dropping expired Cookie: .site.com TRUE / FALSE 1192655365 FORMCRED > 2008/04/14 17:09:26 DEBUG - jmeter.protocol.http.control.CookieManager: > Received Cookie: > SMSESSION=DjF8ol8KxlTwGEEDHiJxYeKD91Mr/7ITxILgxBj7+ZFxvQFu4nJUNTApcaVTSCNHlLw9yLI2I9CdE5FAp3JwO9gzbjvZlLzhqf39MvpocOfYbYqh7kjwHN5hjdakQOvg+0k+3vxNNr00J6qd5b9v/fsE5FZME0Jg/WHjoFo8AX58f1hHNcDROoUbtXt99cZhoBq0f+b3S5j14nBauPKgxMylJR76qYv+I1ZJTYqXP2Nxvys5dtsiQgx7wHIvK7sTOb1MJGP705uvV9vgDyZksffgnwb1teUELPgbv+Ma79R64W9JKtdN3Uqy3zh50LEdR2EPAo/eKTE7Lh6iGpm/JpDSWJzeLmAnAZsSv4A8bailiDx9gLz5r8xhumrbzzhAC/gf/a0YE+6VlDqRHPlFoUoDZOyQFxhtgMlRy5osr9TnuxjN4ZVc9TDsgPFmiROYpZvkieAkoopYmgI13UdLEuyNw8G/8pe8uCBi0zWZoiN24zdayozW9WbnAKbLnQt6FEoxdfUhGc8Ag7LnGnH+lWI6dtXBsvioF6ogsrDlwwc6q9QkOuqI4jfY6ao42JLwNPaqHn6mumFJUHz2N+JmfRpvQWbVYkUA+J0aXmYUD869IauIW6hygoK/NXtWPRFqMbSIMQceFR/OINRBj1up4HjnZhpYxVuj2UdR1erdj0mpx2pFVuViUIq8nRyvEPIzF1U0hTPsKVYbGVDmrKtc3SVA66J+vXds+Aq4EzxqyTxyz0J6eDTnv6pxxvpnqlU2d0tx2bs/E3f56+Og3+ig6Wx8oW3u3kFZfQu2+i+52ZgF8DE3sGFmIjBpPvtbz7CFEAm4BezxQ7RTdSoTXJF8YTWgjuI9VOupzrGY+SrJKLDIrDu14lJABOLhYbq9ZBxsymH8wPHTH5MUBLdTmstBTYmAGUb7pqZT6zg44u9LnmB2Q71y/1FYmrUBqj+3eK8sGP/r9wbf4Cy9xQloiUgSAiGkh2HZ5z42S0+7y+NjFrhj11KLIn0KGKIvtt0jam0ktWCdSdaG+3z5ydAkmIqvTn1YfMtRtbGa4yoPuBI7Ynt5E+2GVlEywaXTqUgn1miY; > path=/; domain=.site.c
Odd Cookie Manager behavior
Hey All, I was wondering if anyone could offer some advice on how to deal with an odd issue I'm seeing with my Jmeter test. It's a simple test that logs into a webapp, and it looks roughly like this: Thread group | -HTTPCookieManager -Simple Controller | --Login (HTTP Request that posts the user name and password to a Netegrity Siteminder action) | --Get Homepage (HTTP Request that gets the homepage of the app) -View Results Tree -Aggregate Report I have the "Clear cookies each iteration?" option set to true in my HTTPCookieManager. The thread group has 5 users, with a 1 second ramp up period, and only one iteration. The problem is that when I look at the View Results Tree report, I can see that only the first thread sends the 'Login' action with no cookies. The subsequent 4 threads all send a cookie who's value was set by the previous thread. As suggested on this list, I switched on debugging for the HTTPCookieManager, and got this stack trace: 2008/04/14 17:09:25 INFO - jmeter.engine.StandardJMeterEngine: Running the test! 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: Clear all cookies from store 2008/04/14 17:09:25 INFO - jmeter.gui.util.JMeterMenuBar: setRunning(true,*local*) 2008/04/14 17:09:25 INFO - jmeter.engine.StandardJMeterEngine: Starting 5 threads for group Test Execution. Ramp up = 5. 2008/04/14 17:09:25 INFO - jmeter.engine.StandardJMeterEngine: Continue on error 2008/04/14 17:09:25 INFO - jmeter.threads.JMeterThread: Thread Test Execution 1-1 started 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: Clear all cookies from store 2008/04/14 17:09:25 INFO - jmeter.services.FileServer: Stored: C:\jakarta-jmeter-2.3.1\test plans\users.csv 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: Found 0 cookies for https://my.site.com/suite/login/login.fcc 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: Received Cookie: FORMCRED=ilBWOQVZ8OyBxrpjczIyJuO5Zj9reyJCi3E77fw1VmbC5pSM3ls5KmQbpsjCpwOhDC1MtHLBe3uBJTHMx2qo05Wh2yf3YkD3AiQjVhFUSRVl3eD0vIEu84cQH9uRXVje;path=/; domain=.site.com From: https://my.site.com/suite/login/login.fcc 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: Add cookie to store .site.com TRUE / FALSE 0 FORMCRED ilBWOQVZ8OyBxrpjczIyJuO5Zj9reyJCi3E77fw1VmbC5pSM3ls5KmQbpsjCpwOhDC1MtHLBe3uBJTHMx2qo05Wh2yf3YkD3AiQjVhFUSRVl3eD0vIEu84cQH9uRXVje 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: Found 1 cookies for https://my.site.com/suite/portal/authenticate.do 2008/04/14 17:09:25 DEBUG - jmeter.protocol.http.control.CookieManager: Cookie: FORMCRED=ilBWOQVZ8OyBxrpjczIyJuO5Zj9reyJCi3E77fw1VmbC5pSM3ls5KmQbpsjCpwOhDC1MtHLBe3uBJTHMx2qo05Wh2yf3YkD3AiQjVhFUSRVl3eD0vIEu84cQH9uRXVje 2008/04/14 17:09:26 DEBUG - jmeter.protocol.http.control.CookieManager: Received Cookie: FORMCRED=; path=/; expires=Wed, 17 Oct 2007 21:09:25 GMT; domain=.site.com From: https://my.site.com/suite/portal/authenticate.do 2008/04/14 17:09:26 DEBUG - jmeter.protocol.http.control.CookieManager: New Cookie = .site.com TRUE / FALSE 1192655365 FORMCRED removing matching Cookie .site.com TRUE / FALSE 0 FORMCRED ilBWOQVZ8OyBxrpjczIyJuO5Zj9reyJCi3E77fw1VmbC5pSM3ls5KmQbpsjCpwOhDC1MtHLBe3uBJTHMx2qo05Wh2yf3YkD3AiQjVhFUSRVl3eD0vIEu84cQH9uRXVje 2008/04/14 17:09:26 DEBUG - jmeter.protocol.http.control.CookieManager: Dropping expired Cookie: .site.com TRUE / FALSE 1192655365 FORMCRED 2008/04/14 17:09:26 DEBUG - jmeter.protocol.http.control.CookieManager: Received Cookie: SMSESSION=DjF8ol8KxlTwGEEDHiJxYeKD91Mr/7ITxILgxBj7+ZFxvQFu4nJUNTApcaVTSCNHlLw9yLI2I9CdE5FAp3JwO9gzbjvZlLzhqf39MvpocOfYbYqh7kjwHN5hjdakQOvg+0k+3vxNNr00J6qd5b9v/fsE5FZME0Jg/WHjoFo8AX58f1hHNcDROoUbtXt99cZhoBq0f+b3S5j14nBauPKgxMylJR76qYv+I1ZJTYqXP2Nxvys5dtsiQgx7wHIvK7sTOb1MJGP705uvV9vgDyZksffgnwb1teUELPgbv+Ma79R64W9JKtdN3Uqy3zh50LEdR2EPAo/eKTE7Lh6iGpm/JpDSWJzeLmAnAZsSv4A8bailiDx9gLz5r8xhumrbzzhAC/gf/a0YE+6VlDqRHPlFoUoDZOyQFxhtgMlRy5osr9TnuxjN4ZVc9TDsgPFmiROYpZvkieAkoopYmgI13UdLEuyNw8G/8pe8uCBi0zWZoiN24zdayozW9WbnAKbLnQt6FEoxdfUhGc8Ag7LnGnH+lWI6dtXBsvioF6ogsrDlwwc6q9QkOuqI4jfY6ao42JLwNPaqHn6mumFJUHz2N+JmfRpvQWbVYkUA+J0aXmYUD869IauIW6hygoK/NXtWPRFqMbSIMQceFR/OINRBj1up4HjnZhpYxVuj2UdR1erdj0mpx2pFVuViUIq8nRyvEPIzF1U0hTPsKVYbGVDmrKtc3SVA66J+vXds+Aq4EzxqyTxyz0J6eDTnv6pxxvpnqlU2d0tx2bs/E3f56+Og3+ig6Wx8oW3u3kFZfQu2+i+52ZgF8DE3sGFmIjBpPvtbz7CFEAm4BezxQ7RTdSoTXJF8YTWgjuI9VOupzrGY+SrJKLDIrDu14lJABOLhYbq9ZBxsymH8wPHTH5MUBLdTmstBTYmAGUb7pqZT6zg44u9LnmB2Q71y/1FYmrUBqj+3eK8sGP/r9wbf4Cy9xQloiUgSAiGkh2HZ5z42S0+7y+NjFrhj11KLIn0KGKIvtt0jam0ktWCdSdaG+3z5ydAkmIqvTn1YfMtRtbGa4yoPuBI7Ynt5E+2GVlEywaXTqUgn1miY; path=/; domain=.site.com From: https://my.site.com/suite/portal/authenticate.do 2008/04/14 17:09:26 DEBUG - jmeter.protocol.http.control.CookieManager: Add cookie to store .site.com TRUE / FALSE 0 SMSESSION DjF8ol8KxlTwGEEDHiJxYeKD91Mr/7ITxILgxBj7+ZFxvQFu4nJUNTApcaVTSCNHlLw9yLI2I9CdE5FAp
Re: how to make Cookie Manager work recursively?
On 22/02/2008, Tom Fernandes <[EMAIL PROTECTED]> wrote: > Hello, > > My test-plan is the following: > > Thread-Group > | > | -- HTTP Request Defaults > | > | -- HTTP Request (http://foo.com) > | > | -- simple Controller > | | > | | -- HTTP Request (http://foo.com/bar.php) > | | > | | -- HTTP Request (http://foo.com/bar.php) > | | > | | -- Gaussian Random Timer > | > | > | -- HTTP Request (http://foo.com/anotherbar.php) > | > | -- Cookie Manager > | >... > > The Cookie Manager works for http://foo.com and http://foo.com/anotherbar.php > but not for http://foo.com/bar.php. > > How can I achieve sending the cookies also in the http://foo.com/bar.php > Request? The placement of the Cookie Manager is fine; perhaps there is a problem with the cookies themselves. Try adding a View Results Tree Listener after the Cookie Manager; you can see the cookies on Sampler Result and Request pages. If you select the Cookie Manager you can then use the Menu item Help/Enable Debug to enable debugging of cookies. This may help. > > thanks, > > > Tom > > - > 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]
how to make Cookie Manager work recursively?
Hello, My test-plan is the following: Thread-Group | | -- HTTP Request Defaults | | -- HTTP Request (http://foo.com) | | -- simple Controller | | | | -- HTTP Request (http://foo.com/bar.php) | | | | -- HTTP Request (http://foo.com/bar.php) | | | | -- Gaussian Random Timer | | | -- HTTP Request (http://foo.com/anotherbar.php) | | -- Cookie Manager | ... The Cookie Manager works for http://foo.com and http://foo.com/anotherbar.php but not for http://foo.com/bar.php. How can I achieve sending the cookies also in the http://foo.com/bar.php Request? thanks, Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with sessions handling using cookie manager
Hi Sebb. I didn´t know this bug. After I read your reply, I was searching more information about it and I find this information: http://www.nabble.com/JMeter-2.3.1-bug-in-Cookie-Manager-%22clear-each-iteration%22-td14343027.html I am using this suggestion: "- add a BeanShell Pre-Processor to the FIRST sampler with the script: sampler.getCookieManager().clear(); Thank you. Flavio sebb wrote: The Cookie Manager should normally be added at the top level of a test. Unfortunately there is a bug in 2.3.1: if you set the "clear cookies each iteration" checkbox, the cookies end up shared between threads, see: http://wiki.apache.org/jakarta-jmeter/CookieManagerBugIn231 On 04/02/2008, Flavio Mendes wrote: > Dear all, > > I am testing an application where I create a folder, update it and remove it. > I am having problems with the "Remove Request". If I add a Cookie Manager > like a child of this Request, the JMeter fails since the second iteration (it > doesn´t remove the folder). I think JMeter tries to remove the folder of the > second iteration in the session of the first iteration. > > If I add a Cookie Manager in the begining of JMeter Script (at the same level > of "Remove Request"), I get problems when I execute scenarios with more than > one user (I see, in "View Results Tree", folders of an user or thread in > requests of other users). If I disable the Cookie Manager, I see the Login > Page when "Remove request" is sent to the server. > > So, I want to work with the folders (creating, updating and removing them) in > session separated (one for each user or thread). I don´t know how to use the > cookie manager to do it. Could somebody help me? > > Thanks > > Flavio > > > - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
Re: Problem with sessions handling using cookie manager
The Cookie Manager should normally be added at the top level of a test. Unfortunately there is a bug in 2.3.1: if you set the "clear cookies each iteration" checkbox, the cookies end up shared between threads, see: http://wiki.apache.org/jakarta-jmeter/CookieManagerBugIn231 On 04/02/2008, Flavio Mendes <[EMAIL PROTECTED]> wrote: > Dear all, > > I am testing an application where I create a folder, update it and remove > it. I am having problems with the "Remove Request". If I add a Cookie Manager > like a child of this Request, the JMeter fails since the second iteration (it > doesn´t remove the folder). I think JMeter tries to remove the folder of the > second iteration in the session of the first iteration. > > If I add a Cookie Manager in the begining of JMeter Script (at the same level > of "Remove Request"), I get problems when I execute scenarios with more than > one user (I see, in "View Results Tree", folders of an user or thread in > requests of other users). If I disable the Cookie Manager, I see the Login > Page when "Remove request" is sent to the server. > > So, I want to work with the folders (creating, updating and removing them) > in session separated (one for each user or thread). I don´t know how to use > the cookie manager to do it. Could somebody help me? > > Thanks > > Flavio > > > - > Abra sua conta no Yahoo! Mail, o único sem limite de espaço para > armazenamento! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with sessions handling using cookie manager
Dear all, I am testing an application where I create a folder, update it and remove it. I am having problems with the "Remove Request". If I add a Cookie Manager like a child of this Request, the JMeter fails since the second iteration (it doesn´t remove the folder). I think JMeter tries to remove the folder of the second iteration in the session of the first iteration. If I add a Cookie Manager in the begining of JMeter Script (at the same level of "Remove Request"), I get problems when I execute scenarios with more than one user (I see, in "View Results Tree", folders of an user or thread in requests of other users). If I disable the Cookie Manager, I see the Login Page when "Remove request" is sent to the server. So, I want to work with the folders (creating, updating and removing them) in session separated (one for each user or thread). I don´t know how to use the cookie manager to do it. Could somebody help me? Thanks Flavio - Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
Sharing a cookie manager
Is there a way to share a cookie manager across threads? I can see that manually created cookies are shared across all threads, but my use case requires my initial thread to instantiate a session and then subsequent threads to execute concurrent requests. I cannot establish sessions in each thread separately with same user because of our security feature preventing same user from having more than one session established at any given time. Any new sessions will invalidate other sessions. So I basically need to establish a session before I can run other thread groups and ensure that my session cookies are shared. Is there a way to accomplish this? Ilya - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JMeter 2.3.1 bug in Cookie Manager "clear each iteration"
The Cookie Manager has an option to "Clear cookies each iteration".
Unfortunately,when the code was updated in 2.3.1 to allow pre-defined
cookies to be preserved, a bug was introduced.
The bug caused cookie handling to break - all threads end up sharing
the same cookies. [If "clear each iteration" is not selected, then
cookies are handled OK]
==
The code has been fixed, and will be in the next release. In the
meantime, if you need the feature, some workrounds are:
- use JMeter 2.3
-- or --
- add a BeanShell Pre-Processor to the FIRST sampler with the script:
sampler.getCookieManager().clear();
-- or --
- add a User Parameters Pre-Processor to the FIRST sampler:
Name: DUMMY
User_1: ${__jexl(sampler.getCookieManager().clear())}
[The name DUMMY could be any variable that you are not currently using]
Apologies for any inconvenience.
S///
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cookie manager
--- sebb <[EMAIL PROTECTED]> wrote: > > Works fine for me. Hate when that happens. I loaded a jmx created in an earlier version of Jmeter and the cookie policy can be changed no problem. Not sure if this a clue to my problem. I will try re-creating the jmx and see if that fixes things. > > > The other problem is more important. The cookie > > manager doesn't seem to work. I've changed it's > scope > > but still doesn't work. > > It works fine for me with the default policy and > with rfc2109. > > I just tried with Google and the second sampler sent > the cookie > provided by the first response, at least in GUI > mode. > > Try enabling debug for > jmeter.protocol.http.control.CookieManager I will try this, thanks. > > > I edit the test plan in the gui and run the test > > without a gui. > > Does it work in GUI mode for you? I haven't tried running the test in GUI mode since it's a remote box. Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cookie manager
On 04/10/2007, Richard Hubbell <[EMAIL PROTECTED]> wrote: > Couple of things with the cookie manager. I'm using > Jmeter 2.3. The cookie manager defaults to Cookie > policy rfc2109, if I change it, it switches back to > rfc2109 and there's no way other than editing the jmx > by hand to change it, the gui, switches back to > rfc2109. A minor problem. Maybe a java issue?? Works fine for me. > The other problem is more important. The cookie > manager doesn't seem to work. I've changed it's scope > but still doesn't work. It works fine for me with the default policy and with rfc2109. I just tried with Google and the second sampler sent the cookie provided by the first response, at least in GUI mode. Try enabling debug for jmeter.protocol.http.control.CookieManager > I edit the test plan in the gui and run the test > without a gui. Does it work in GUI mode for you? > > > Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos. > http://autos.yahoo.com/index.html > > > > > - > 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]
Cookie manager
Couple of things with the cookie manager. I'm using Jmeter 2.3. The cookie manager defaults to Cookie policy rfc2109, if I change it, it switches back to rfc2109 and there's no way other than editing the jmx by hand to change it, the gui, switches back to rfc2109. A minor problem. Maybe a java issue?? The other problem is more important. The cookie manager doesn't seem to work. I've changed it's scope but still doesn't work. I edit the test plan in the gui and run the test without a gui. Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos. http://autos.yahoo.com/index.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Http Cookie Manager and jsessionid
Thank you! That was it. SOAP/XML-RPC worked great. sebb-2 wrote: > > I don't think that is possible with the WebService(SOAP) sampler. > > Try the SOAP/XML-RPC sampler (or plain HTTP sampler) instead. > > On 02/10/2007, Daniel Herbison <[EMAIL PROTECTED]> wrote: >> >> I want to beable to keep the same jsessionid for two calls to a soap >> service. >> WIll the HTTP Cookie Manager do this? I've tried: >> +Thread Group >> ++HTTP Cookie Manager >> ++WebService(SOAP) Request >> ++WebService(SOAP) Request >> ++View Results Tree >> >> but the second request always gets a different session id. How do I keep >> the two request in the same session? I'm new to JMeter are there >> examples >> of this somewhere? >> -- >> View this message in context: >> http://www.nabble.com/Http-Cookie-Manager-and-jsessionid-tf4555297.html#a13000358 >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> - >> 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] > > > -- View this message in context: http://www.nabble.com/Http-Cookie-Manager-and-jsessionid-tf4555297.html#a13000909 Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Http Cookie Manager and jsessionid
I don't think that is possible with the WebService(SOAP) sampler. Try the SOAP/XML-RPC sampler (or plain HTTP sampler) instead. On 02/10/2007, Daniel Herbison <[EMAIL PROTECTED]> wrote: > > I want to beable to keep the same jsessionid for two calls to a soap service. > WIll the HTTP Cookie Manager do this? I've tried: > +Thread Group > ++HTTP Cookie Manager > ++WebService(SOAP) Request > ++WebService(SOAP) Request > ++View Results Tree > > but the second request always gets a different session id. How do I keep > the two request in the same session? I'm new to JMeter are there examples > of this somewhere? > -- > View this message in context: > http://www.nabble.com/Http-Cookie-Manager-and-jsessionid-tf4555297.html#a13000358 > Sent from the JMeter - User mailing list archive at Nabble.com. > > > - > 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]
Http Cookie Manager and jsessionid
I want to beable to keep the same jsessionid for two calls to a soap service. WIll the HTTP Cookie Manager do this? I've tried: +Thread Group ++HTTP Cookie Manager ++WebService(SOAP) Request ++WebService(SOAP) Request ++View Results Tree but the second request always gets a different session id. How do I keep the two request in the same session? I'm new to JMeter are there examples of this somewhere? -- View this message in context: http://www.nabble.com/Http-Cookie-Manager-and-jsessionid-tf4555297.html#a13000358 Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager
This is absolutely great! Thanks so much! -Original Message- From: sebb [mailto:[EMAIL PROTECTED] Sent: 14 August 2007 13:12 To: JMeter Users List Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager The latest nightly (r565714) includes what I hope is a work-round for the NPE - a message should be logged instead. S. On 14/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > Great stuff! This is great support! > > Simon > > -Original Message- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: 14 August 2007 11:29 > To: JMeter Users List > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > Cookie Manager > > This NPE is caused when the list of extracted URLs contains a null > entry - not sure how that happens yet, but I'll put in a check for it. > > On 14/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > Another error message I'm getting is: > > > > 2007/08/14 09:20:09 ERROR - jmeter.threads.JMeterThread: > > java.lang.NullPointerException > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.downloadPageReso > > urces(HTTPSamplerBase.java:1030) > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.resultProcessing > > (HTTPSamplerBase.java:1253) > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HTTPSampler2 > > .java:853) > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl > > erBase.java:889) > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl > > erBase.java:875) > >at > > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:298) > >at java.lang.Thread.run(Thread.java:619) > > > > 2007/08/14 09:20:09 WARN - > > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > > Header Manager superseded by HTTP Header Manager > > 2007/08/14 09:20:09 WARN - > > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > > Cookie Manager superseded by HTTP Cookie Manager > > > > Simon > > > > -Original Message- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: 13 August 2007 17:51 > > To: JMeter Users List > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > Cookie Manager > > > > I've just uploaded r565388 to the nightly directory - this should fix > > the redirect NPE (as well as the Summariser bug) > > > > S. > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > Thanks Sebb, > > > > > > Have upgraded to the latest nightly build and am running the suite > > > against it. Have also modified my Test Plan as you suggested. > > > > > > Many thanks, > > > > > > Simon > > > > > > -Original Message- > > > From: sebb [mailto:[EMAIL PROTECTED] > > > Sent: 13 August 2007 16:27 > > > To: JMeter Users List > > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > > Cookie Manager > > > > > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > > Hi Sebb, > > > > > > > > Many thanks again. > > > > > > > > I'm aware that a redirect response with no location header is a > HTTP > > > > protocol violation, but I'm running through a suite of URLs > provided > > > by > > > > a third party and quite a number of them contain this. Can JMeter > > > just > > > > ignore that URL if a HTTP Protocol violation takes place? > > > > > > That's what should happen once the NPE bug is fixed. > > > > > > > I'm using JMeter 2.3RC3. > > > > > > > > I'm also getting another NullPointerException with the following > > > error: > > > > > > > > 007/08/13 14:57:52 ERROR - jmeter.threads.ListenerNotifier: > Detected > > > > problem in Listener: java.lang.NullPointerException > > > >at > > > > > > > > > > org.apache.jmeter.reporters.Summariser$Totals.access$200(Summariser.java > > > > :130) > > > > > > Yes, unfortunately the summariser is broken in 2.3RC3; remove it or > > > try the latest nightly. > > > > > > >at > > > > > > > > > > org.apache.jmeter.reporters.Summariser.sampleOccurred(Summariser.java:19
Re: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager
The latest nightly (r565714) includes what I hope is a work-round for the NPE - a message should be logged instead. S. On 14/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > Great stuff! This is great support! > > Simon > > -Original Message- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: 14 August 2007 11:29 > To: JMeter Users List > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > Cookie Manager > > This NPE is caused when the list of extracted URLs contains a null > entry - not sure how that happens yet, but I'll put in a check for it. > > On 14/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > Another error message I'm getting is: > > > > 2007/08/14 09:20:09 ERROR - jmeter.threads.JMeterThread: > > java.lang.NullPointerException > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.downloadPageReso > > urces(HTTPSamplerBase.java:1030) > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.resultProcessing > > (HTTPSamplerBase.java:1253) > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HTTPSampler2 > > .java:853) > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl > > erBase.java:889) > >at > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl > > erBase.java:875) > >at > > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:298) > >at java.lang.Thread.run(Thread.java:619) > > > > 2007/08/14 09:20:09 WARN - > > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > > Header Manager superseded by HTTP Header Manager > > 2007/08/14 09:20:09 WARN - > > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > > Cookie Manager superseded by HTTP Cookie Manager > > > > Simon > > > > -Original Message- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: 13 August 2007 17:51 > > To: JMeter Users List > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > Cookie Manager > > > > I've just uploaded r565388 to the nightly directory - this should fix > > the redirect NPE (as well as the Summariser bug) > > > > S. > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > Thanks Sebb, > > > > > > Have upgraded to the latest nightly build and am running the suite > > > against it. Have also modified my Test Plan as you suggested. > > > > > > Many thanks, > > > > > > Simon > > > > > > -Original Message- > > > From: sebb [mailto:[EMAIL PROTECTED] > > > Sent: 13 August 2007 16:27 > > > To: JMeter Users List > > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > > Cookie Manager > > > > > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > > Hi Sebb, > > > > > > > > Many thanks again. > > > > > > > > I'm aware that a redirect response with no location header is a > HTTP > > > > protocol violation, but I'm running through a suite of URLs > provided > > > by > > > > a third party and quite a number of them contain this. Can JMeter > > > just > > > > ignore that URL if a HTTP Protocol violation takes place? > > > > > > That's what should happen once the NPE bug is fixed. > > > > > > > I'm using JMeter 2.3RC3. > > > > > > > > I'm also getting another NullPointerException with the following > > > error: > > > > > > > > 007/08/13 14:57:52 ERROR - jmeter.threads.ListenerNotifier: > Detected > > > > problem in Listener: java.lang.NullPointerException > > > >at > > > > > > > > > > org.apache.jmeter.reporters.Summariser$Totals.access$200(Summariser.java > > > > :130) > > > > > > Yes, unfortunately the summariser is broken in 2.3RC3; remove it or > > > try the latest nightly. > > > > > > >at > > > > > > > > > > org.apache.jmeter.reporters.Summariser.sampleOccurred(Summariser.java:19 > > > > 0) > > > >at > > > > > > > > > > org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotif > > > > ier.java:240) > > > >at > &g
RE: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager
Great stuff! This is great support! Simon -Original Message- From: sebb [mailto:[EMAIL PROTECTED] Sent: 14 August 2007 11:29 To: JMeter Users List Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager This NPE is caused when the list of extracted URLs contains a null entry - not sure how that happens yet, but I'll put in a check for it. On 14/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > Another error message I'm getting is: > > 2007/08/14 09:20:09 ERROR - jmeter.threads.JMeterThread: > java.lang.NullPointerException >at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.downloadPageReso > urces(HTTPSamplerBase.java:1030) >at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.resultProcessing > (HTTPSamplerBase.java:1253) >at > org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HTTPSampler2 > .java:853) >at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl > erBase.java:889) >at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl > erBase.java:875) >at > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:298) >at java.lang.Thread.run(Thread.java:619) > > 2007/08/14 09:20:09 WARN - > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > Header Manager superseded by HTTP Header Manager > 2007/08/14 09:20:09 WARN - > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > Cookie Manager superseded by HTTP Cookie Manager > > Simon > > -Original Message- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: 13 August 2007 17:51 > To: JMeter Users List > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > Cookie Manager > > I've just uploaded r565388 to the nightly directory - this should fix > the redirect NPE (as well as the Summariser bug) > > S. > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > Thanks Sebb, > > > > Have upgraded to the latest nightly build and am running the suite > > against it. Have also modified my Test Plan as you suggested. > > > > Many thanks, > > > > Simon > > > > -Original Message- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: 13 August 2007 16:27 > > To: JMeter Users List > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > Cookie Manager > > > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > Hi Sebb, > > > > > > Many thanks again. > > > > > > I'm aware that a redirect response with no location header is a HTTP > > > protocol violation, but I'm running through a suite of URLs provided > > by > > > a third party and quite a number of them contain this. Can JMeter > > just > > > ignore that URL if a HTTP Protocol violation takes place? > > > > That's what should happen once the NPE bug is fixed. > > > > > I'm using JMeter 2.3RC3. > > > > > > I'm also getting another NullPointerException with the following > > error: > > > > > > 007/08/13 14:57:52 ERROR - jmeter.threads.ListenerNotifier: Detected > > > problem in Listener: java.lang.NullPointerException > > >at > > > > > > org.apache.jmeter.reporters.Summariser$Totals.access$200(Summariser.java > > > :130) > > > > Yes, unfortunately the summariser is broken in 2.3RC3; remove it or > > try the latest nightly. > > > > >at > > > > > > org.apache.jmeter.reporters.Summariser.sampleOccurred(Summariser.java:19 > > > 0) > > >at > > > > > > org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotif > > > ier.java:240) > > >at > > > > > > org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java > > > :572) > > >at > > > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:309) > > >at java.lang.Thread.run(Thread.java:619) > > > > > > I've tried removing and rearranging some of the header managers, but > > > with no success. > > > > > > My current arrangement is as follows: > > > > > > Test Plan > > > + HTTP Header Manager > > > + Thread Group > > > + While Controller > > > + + CSV Data Set Config > > > + + HTTP Request HTTPClient > > > + + + Bean Shell Listener > > > + + HTTP Cookie Manager > > >
Re: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager
This NPE is caused when the list of extracted URLs contains a null entry - not sure how that happens yet, but I'll put in a check for it. On 14/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > Another error message I'm getting is: > > 2007/08/14 09:20:09 ERROR - jmeter.threads.JMeterThread: > java.lang.NullPointerException >at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.downloadPageReso > urces(HTTPSamplerBase.java:1030) >at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.resultProcessing > (HTTPSamplerBase.java:1253) >at > org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HTTPSampler2 > .java:853) >at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl > erBase.java:889) >at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl > erBase.java:875) >at > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:298) >at java.lang.Thread.run(Thread.java:619) > > 2007/08/14 09:20:09 WARN - > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > Header Manager superseded by HTTP Header Manager > 2007/08/14 09:20:09 WARN - > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > Cookie Manager superseded by HTTP Cookie Manager > > Simon > > -Original Message- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: 13 August 2007 17:51 > To: JMeter Users List > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > Cookie Manager > > I've just uploaded r565388 to the nightly directory - this should fix > the redirect NPE (as well as the Summariser bug) > > S. > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > Thanks Sebb, > > > > Have upgraded to the latest nightly build and am running the suite > > against it. Have also modified my Test Plan as you suggested. > > > > Many thanks, > > > > Simon > > > > -Original Message- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: 13 August 2007 16:27 > > To: JMeter Users List > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > Cookie Manager > > > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > Hi Sebb, > > > > > > Many thanks again. > > > > > > I'm aware that a redirect response with no location header is a HTTP > > > protocol violation, but I'm running through a suite of URLs provided > > by > > > a third party and quite a number of them contain this. Can JMeter > > just > > > ignore that URL if a HTTP Protocol violation takes place? > > > > That's what should happen once the NPE bug is fixed. > > > > > I'm using JMeter 2.3RC3. > > > > > > I'm also getting another NullPointerException with the following > > error: > > > > > > 007/08/13 14:57:52 ERROR - jmeter.threads.ListenerNotifier: Detected > > > problem in Listener: java.lang.NullPointerException > > >at > > > > > > org.apache.jmeter.reporters.Summariser$Totals.access$200(Summariser.java > > > :130) > > > > Yes, unfortunately the summariser is broken in 2.3RC3; remove it or > > try the latest nightly. > > > > >at > > > > > > org.apache.jmeter.reporters.Summariser.sampleOccurred(Summariser.java:19 > > > 0) > > >at > > > > > > org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotif > > > ier.java:240) > > >at > > > > > > org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java > > > :572) > > >at > > > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:309) > > >at java.lang.Thread.run(Thread.java:619) > > > > > > I've tried removing and rearranging some of the header managers, but > > > with no success. > > > > > > My current arrangement is as follows: > > > > > > Test Plan > > > + HTTP Header Manager > > > + Thread Group > > > + While Controller > > > + + CSV Data Set Config > > > + + HTTP Request HTTPClient > > > + + + Bean Shell Listener > > > + + HTTP Cookie Manager > > > + + View Results in Table Listener > > > > It would be better to use: > > > > Test Plan > > + Thread Group > > + + HTTP Header Manager > > + + HTTP Cookie Manager > > + + While Cont
RE: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager
Hi Sebb, Thank you very much for your help! There was no more trace at the time I captured that message. However I subsequently got another trace: 2007/08/14 09:20:09 ERROR - jmeter.threads.JMeterThread: java.lang.NullPointerException at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.downloadPageReso urces(HTTPSamplerBase.java:1030) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.resultProcessing (HTTPSamplerBase.java:1253) at org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HTTPSampler2 .java:853) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl erBase.java:889) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl erBase.java:875) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:298) at java.lang.Thread.run(Thread.java:619) 2007/08/14 09:20:09 WARN - jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP Header Manager superseded by HTTP Header Manager 2007/08/14 09:20:09 WARN - jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager I'll send the JMX to you privately. Many thanks indeed. Simon -Original Message- From: sebb [mailto:[EMAIL PROTECTED] Sent: 14 August 2007 10:33 To: JMeter Users List Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager On 14/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > Hi Seb, > > Thanks for all your help. That uploaded nightly build seems to have > greatly improved the processing of my suite of urls. > > However, I'm still seeing the following error reported, although it > doesn't seem to cause JMeter to stop processing the URLs: > > 2007/08/14 08:41:29 ERROR - jmeter.threads.JMeterThread: > java.lang.NullPointerException Is there no more trace? e.g. line numbers? > 2007/08/14 08:41:29 WARN - > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > Header Manager superseded by HTTP Header Manager > 2007/08/14 08:41:29 WARN - > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > Cookie Manager superseded by HTTP Cookie Manager I don't understand that - can you send me the JMX privately? > The layout of my Test Plan is as follows: > > Test Plan > + Thread Group > + + HTTP Header Manager > + + HTTP Cookie Manager > + + While Controller > + + + CSV Data Set Config > + + + HTTP Request HTTPClient > + + + + Bean Shell Listener > + View Results in Table Listener > > Any thoughts? > > Regards, > > Simon > > -Original Message- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: 13 August 2007 17:51 > To: JMeter Users List > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > Cookie Manager > > I've just uploaded r565388 to the nightly directory - this should fix > the redirect NPE (as well as the Summariser bug) > > S. > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > Thanks Sebb, > > > > Have upgraded to the latest nightly build and am running the suite > > against it. Have also modified my Test Plan as you suggested. > > > > Many thanks, > > > > Simon > > > > -Original Message- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: 13 August 2007 16:27 > > To: JMeter Users List > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > Cookie Manager > > > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > Hi Sebb, > > > > > > Many thanks again. > > > > > > I'm aware that a redirect response with no location header is a HTTP > > > protocol violation, but I'm running through a suite of URLs provided > > by > > > a third party and quite a number of them contain this. Can JMeter > > just > > > ignore that URL if a HTTP Protocol violation takes place? > > > > That's what should happen once the NPE bug is fixed. > > > > > I'm using JMeter 2.3RC3. > > > > > > I'm also getting another NullPointerException with the following > > error: > > > > > > 007/08/13 14:57:52 ERROR - jmeter.threads.ListenerNotifier: Detected > > > problem in Listener: java.lang.NullPointerException > > >at > > > > > > org.apache.jmeter.reporters.Summariser$Totals.access$200(Summariser.java > > > :130) > > > > Yes, unfortunately the summariser is broken in 2.3RC3; remove it or > > try the latest nightly. > > > > >at > > > > > > org.apache.jmeter.reporters.Summariser.sample
Re: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager
On 14/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > Hi Seb, > > Thanks for all your help. That uploaded nightly build seems to have > greatly improved the processing of my suite of urls. > > However, I'm still seeing the following error reported, although it > doesn't seem to cause JMeter to stop processing the URLs: > > 2007/08/14 08:41:29 ERROR - jmeter.threads.JMeterThread: > java.lang.NullPointerException Is there no more trace? e.g. line numbers? > 2007/08/14 08:41:29 WARN - > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > Header Manager superseded by HTTP Header Manager > 2007/08/14 08:41:29 WARN - > jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP > Cookie Manager superseded by HTTP Cookie Manager I don't understand that - can you send me the JMX privately? > The layout of my Test Plan is as follows: > > Test Plan > + Thread Group > + + HTTP Header Manager > + + HTTP Cookie Manager > + + While Controller > + + + CSV Data Set Config > + + + HTTP Request HTTPClient > + + + + Bean Shell Listener > + View Results in Table Listener > > Any thoughts? > > Regards, > > Simon > > -Original Message- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: 13 August 2007 17:51 > To: JMeter Users List > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > Cookie Manager > > I've just uploaded r565388 to the nightly directory - this should fix > the redirect NPE (as well as the Summariser bug) > > S. > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > Thanks Sebb, > > > > Have upgraded to the latest nightly build and am running the suite > > against it. Have also modified my Test Plan as you suggested. > > > > Many thanks, > > > > Simon > > > > -Original Message- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: 13 August 2007 16:27 > > To: JMeter Users List > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > Cookie Manager > > > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > Hi Sebb, > > > > > > Many thanks again. > > > > > > I'm aware that a redirect response with no location header is a HTTP > > > protocol violation, but I'm running through a suite of URLs provided > > by > > > a third party and quite a number of them contain this. Can JMeter > > just > > > ignore that URL if a HTTP Protocol violation takes place? > > > > That's what should happen once the NPE bug is fixed. > > > > > I'm using JMeter 2.3RC3. > > > > > > I'm also getting another NullPointerException with the following > > error: > > > > > > 007/08/13 14:57:52 ERROR - jmeter.threads.ListenerNotifier: Detected > > > problem in Listener: java.lang.NullPointerException > > >at > > > > > > org.apache.jmeter.reporters.Summariser$Totals.access$200(Summariser.java > > > :130) > > > > Yes, unfortunately the summariser is broken in 2.3RC3; remove it or > > try the latest nightly. > > > > >at > > > > > > org.apache.jmeter.reporters.Summariser.sampleOccurred(Summariser.java:19 > > > 0) > > >at > > > > > > org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotif > > > ier.java:240) > > > at > > > > > > org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java > > > :572) > > >at > > > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:309) > > >at java.lang.Thread.run(Thread.java:619) > > > > > > I've tried removing and rearranging some of the header managers, but > > > with no success. > > > > > > My current arrangement is as follows: > > > > > > Test Plan > > > + HTTP Header Manager > > > + Thread Group > > > + While Controller > > > + + CSV Data Set Config > > > + + HTTP Request HTTPClient > > > + + + Bean Shell Listener > > > + + HTTP Cookie Manager > > > + + View Results in Table Listener > > > > It would be better to use: > > > > Test Plan > > + Thread Group > > + + HTTP Header Manager > > + + HTTP Cookie Manager > > + + While Controller > > + + + CSV Data Set Config > > + + + HTTP Request HTTPClient > > + + + + Bean Shell Listen
RE: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager
Another error message I'm getting is: 2007/08/14 09:20:09 ERROR - jmeter.threads.JMeterThread: java.lang.NullPointerException at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.downloadPageReso urces(HTTPSamplerBase.java:1030) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.resultProcessing (HTTPSamplerBase.java:1253) at org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HTTPSampler2 .java:853) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl erBase.java:889) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSampl erBase.java:875) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:298) at java.lang.Thread.run(Thread.java:619) 2007/08/14 09:20:09 WARN - jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP Header Manager superseded by HTTP Header Manager 2007/08/14 09:20:09 WARN - jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager Simon -Original Message- From: sebb [mailto:[EMAIL PROTECTED] Sent: 13 August 2007 17:51 To: JMeter Users List Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager I've just uploaded r565388 to the nightly directory - this should fix the redirect NPE (as well as the Summariser bug) S. On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > Thanks Sebb, > > Have upgraded to the latest nightly build and am running the suite > against it. Have also modified my Test Plan as you suggested. > > Many thanks, > > Simon > > -Original Message- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: 13 August 2007 16:27 > To: JMeter Users List > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > Cookie Manager > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > Hi Sebb, > > > > Many thanks again. > > > > I'm aware that a redirect response with no location header is a HTTP > > protocol violation, but I'm running through a suite of URLs provided > by > > a third party and quite a number of them contain this. Can JMeter > just > > ignore that URL if a HTTP Protocol violation takes place? > > That's what should happen once the NPE bug is fixed. > > > I'm using JMeter 2.3RC3. > > > > I'm also getting another NullPointerException with the following > error: > > > > 007/08/13 14:57:52 ERROR - jmeter.threads.ListenerNotifier: Detected > > problem in Listener: java.lang.NullPointerException > >at > > > org.apache.jmeter.reporters.Summariser$Totals.access$200(Summariser.java > > :130) > > Yes, unfortunately the summariser is broken in 2.3RC3; remove it or > try the latest nightly. > > >at > > > org.apache.jmeter.reporters.Summariser.sampleOccurred(Summariser.java:19 > > 0) > >at > > > org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotif > > ier.java:240) > >at > > > org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java > > :572) > >at > > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:309) > >at java.lang.Thread.run(Thread.java:619) > > > > I've tried removing and rearranging some of the header managers, but > > with no success. > > > > My current arrangement is as follows: > > > > Test Plan > > + HTTP Header Manager > > + Thread Group > > + While Controller > > + + CSV Data Set Config > > + + HTTP Request HTTPClient > > + + + Bean Shell Listener > > + + HTTP Cookie Manager > > + + View Results in Table Listener > > It would be better to use: > > Test Plan > + Thread Group > + + HTTP Header Manager > + + HTTP Cookie Manager > + + While Controller > + + + CSV Data Set Config > + + + HTTP Request HTTPClient > + + + + Bean Shell Listener > + + View Results in Table Listener > > > Thanks, > > > > Simon > > > > > > -Original Message- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: 13 August 2007 15:36 > > To: JMeter Users List > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > Cookie Manager > > > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > I'm getting the following errors in my jmeter.log file: > > > > > > 2007/08/13 09:13:32 ERROR - > > > org.apache.commons.httpclient.HttpMethodDirector: Received redirect > > > response 302 but no location header > &
RE: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager
Hi Seb, Thanks for all your help. That uploaded nightly build seems to have greatly improved the processing of my suite of urls. However, I'm still seeing the following error reported, although it doesn't seem to cause JMeter to stop processing the URLs: 2007/08/14 08:41:29 ERROR - jmeter.threads.JMeterThread: java.lang.NullPointerException 2007/08/14 08:41:29 WARN - jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP Header Manager superseded by HTTP Header Manager 2007/08/14 08:41:29 WARN - jmeter.protocol.http.sampler.HTTPSamplerBase: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager The layout of my Test Plan is as follows: Test Plan + Thread Group + + HTTP Header Manager + + HTTP Cookie Manager + + While Controller + + + CSV Data Set Config + + + HTTP Request HTTPClient + + + + Bean Shell Listener + View Results in Table Listener Any thoughts? Regards, Simon -Original Message- From: sebb [mailto:[EMAIL PROTECTED] Sent: 13 August 2007 17:51 To: JMeter Users List Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP Cookie Manager I've just uploaded r565388 to the nightly directory - this should fix the redirect NPE (as well as the Summariser bug) S. On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > Thanks Sebb, > > Have upgraded to the latest nightly build and am running the suite > against it. Have also modified my Test Plan as you suggested. > > Many thanks, > > Simon > > -Original Message- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: 13 August 2007 16:27 > To: JMeter Users List > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > Cookie Manager > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > Hi Sebb, > > > > Many thanks again. > > > > I'm aware that a redirect response with no location header is a HTTP > > protocol violation, but I'm running through a suite of URLs provided > by > > a third party and quite a number of them contain this. Can JMeter > just > > ignore that URL if a HTTP Protocol violation takes place? > > That's what should happen once the NPE bug is fixed. > > > I'm using JMeter 2.3RC3. > > > > I'm also getting another NullPointerException with the following > error: > > > > 007/08/13 14:57:52 ERROR - jmeter.threads.ListenerNotifier: Detected > > problem in Listener: java.lang.NullPointerException > >at > > > org.apache.jmeter.reporters.Summariser$Totals.access$200(Summariser.java > > :130) > > Yes, unfortunately the summariser is broken in 2.3RC3; remove it or > try the latest nightly. > > >at > > > org.apache.jmeter.reporters.Summariser.sampleOccurred(Summariser.java:19 > > 0) > >at > > > org.apache.jmeter.threads.ListenerNotifier.notifyListeners(ListenerNotif > > ier.java:240) > >at > > > org.apache.jmeter.threads.JMeterThread.notifyListeners(JMeterThread.java > > :572) > >at > > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:309) > >at java.lang.Thread.run(Thread.java:619) > > > > I've tried removing and rearranging some of the header managers, but > > with no success. > > > > My current arrangement is as follows: > > > > Test Plan > > + HTTP Header Manager > > + Thread Group > > + While Controller > > + + CSV Data Set Config > > + + HTTP Request HTTPClient > > + + + Bean Shell Listener > > + + HTTP Cookie Manager > > + + View Results in Table Listener > > It would be better to use: > > Test Plan > + Thread Group > + + HTTP Header Manager > + + HTTP Cookie Manager > + + While Controller > + + + CSV Data Set Config > + + + HTTP Request HTTPClient > + + + + Bean Shell Listener > + + View Results in Table Listener > > > Thanks, > > > > Simon > > > > > > -Original Message- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: 13 August 2007 15:36 > > To: JMeter Users List > > Subject: Re: Existing Manager HTTP Cookie Manager superseded by HTTP > > Cookie Manager > > > > On 13/08/07, Simon Brown <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > I'm getting the following errors in my jmeter.log file: > > > > > > 2007/08/13 09:13:32 ERROR - > > > org.apache.commons.httpclient.HttpMethodDirector: Received redirect > > > response 302 but no location header > > > > Complain to the server administrator, as it indicates an HTTP protocol > > violation. > > > > > 2
